JP2006226805A - On-vehicle failure diagnosis system - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide an on-vehicle failure diagnosis system capable of facilitating maintenance and repair of vehicles. <P>SOLUTION: An ECU 10 functions as the on-vehicle diagnostic system for detecting various abnormalities in the vehicle 1 as diag-codes, showing the abnormality content. The ECU 10 has previously stored an abnormal component inferring table where combinations of diag-codes are made to correspond to abnormal components inferred as being the cause, when a plurality of diag-codes included in the combinations are detected simultaneously. When the plurality of diag codes are detected simultaneously, the ECU 10 specifies the abnormal components inferred as being the cause, based on the abnormal component inferring table. <P>COPYRIGHT: (C)2006,JPO&NCIPI

Description

  The present invention relates to a vehicle-mounted fault diagnosis device that detects various abnormalities in a vehicle as diagnosis codes (fault codes) indicating the contents of the abnormalities.

  2. Description of the Related Art Conventionally, a vehicle such as an automobile is equipped with an in-vehicle failure diagnosis device (an in-vehicle diagnosis device) that detects an abnormality of the vehicle based on output signals of various sensors. In particular, in recent years, it is called an OBD system (On-Board Diagnostic System), and is required to equip vehicles in and outside Japan.

  Hereinafter, this vehicle-mounted failure diagnosis apparatus will be briefly described. The vehicle-mounted failure diagnosis apparatus monitors and detects various abnormalities in the vehicle, and stores a diagnosis code (hereinafter referred to as “diag code”) corresponding to the detected abnormality content in a memory. In service sites such as maintenance shops and repair shops, a portable fault diagnosis tool (also called a scan tool or the like) is connected to the in-vehicle fault diagnosis device via a cable or the like. Then, the in-vehicle failure diagnosis device sends the diagnostic code stored in the memory to the failure diagnosis tool in response to a request from the failure diagnosis tool. The failure diagnosis tool displays the received diagnostic code on its display. The diagnostic code displayed on the display is read by an operator and used for vehicle maintenance and repair.

  Thus, according to the in-vehicle type failure diagnosis apparatus, the abnormality content of the vehicle can be grasped by the diagnosis code, and the maintenance work and the repair work can be facilitated.

JP 2001-325119 A JP 2003-50701 A Japanese Patent Laid-Open No. 9-16255

  However, the above-described conventional vehicle-mounted fault diagnosis device has the following problems. In a vehicle, when an abnormality occurs in a certain part, a plurality of abnormal phenomena may occur due to the abnormality. In this case, a plurality of diagnostic codes corresponding to a plurality of abnormal phenomena are generated in the above-described in-vehicle type failure diagnosis apparatus. Then, at the service site, the plurality of diag codes are displayed on the failure diagnosis tool. In such a case, it is very difficult to identify one abnormal part from a plurality of diagnostic codes at a service site in a highly complex modern vehicle. For this reason, in an actual service site, a situation where it takes a very long time to identify an abnormal part or a situation where all parts related to a plurality of diagnostic codes are exchanged have occurred.

  Therefore, the present invention provides an in-vehicle failure diagnosis apparatus that can facilitate vehicle maintenance and repair.

  The present invention relates to an in-vehicle failure diagnosis apparatus that detects various abnormalities in a vehicle as a diagnostic code indicating the abnormal contents, and when a combination of diagnostic codes and a plurality of diagnostic codes included in the combination are detected at the same time, Table storage means for storing in advance an abnormal part estimation table associated with an abnormal part estimated as a cause, and abnormal parts stored in the table storage means when a plurality of diagnostic codes are detected at the same time And an abnormal part specifying means for specifying an abnormal part estimated as the cause based on the estimation table.

  In a preferred aspect of the present invention, the vehicle-mounted failure diagnosis device includes an abnormal part data storage unit that stores abnormal part data indicating the abnormal part specified by the abnormal part specifying unit, and a request from a failure diagnosis tool outside the vehicle. And an abnormal part data output means for outputting the abnormal part data stored in the abnormal part data storage means to the failure diagnosis tool.

  ADVANTAGE OF THE INVENTION According to this invention, the vehicle-mounted type failure diagnostic apparatus which can aim at the maintenance of a vehicle and the ease of repair can be provided.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings.

  FIG. 1 is a schematic diagram showing a schematic configuration of a failure diagnosis system 100 including an in-vehicle failure diagnosis apparatus according to the present embodiment. In FIG. 1, the vehicle 1 may be an appropriate vehicle such as an internal combustion engine vehicle or an electric vehicle, but here is a hybrid vehicle using a gasoline engine and an electric motor as drive sources. The vehicle 1 is equipped with an ECU (Electronic Control Unit) 10.

  The ECU 10 is an electronic control device that performs various processes such as engine control, and includes a CPU, a ROM, a RAM, and the like. This ECU 10 functions as an in-vehicle type fault diagnosis apparatus according to the present embodiment. That is, the ECU 10 performs a failure diagnosis of the vehicle 1 and stores a failure diagnosis result therein. More specifically, the ECU 10 detects various abnormalities in the vehicle 1 as a diagnostic code indicating the abnormal contents, and stores a failure diagnosis result including the detected diagnostic code. A failure diagnosis connector 30 is connected to the ECU 10 via a cable 20.

  The failure diagnosis connector 30 is a connector for exchanging data between the ECU 10 and an external device, and is provided at an appropriate location that can be connected to the external device. When maintenance or repair of the vehicle 1 is performed, the failure diagnosis tool 3 is connected to the failure diagnosis connector 30 via the cable 2.

  The failure diagnosis tool 3 is a terminal outside the vehicle provided in a service site such as a maintenance shop or a repair shop, and reads out a failure diagnosis result such as a diagnosis code from the ECU 10 and displays it on the display. The failure diagnosis tool 3 is also called a scan tool or a diagnostic tester, and is generally a portable terminal.

  FIG. 2 is a block diagram showing a functional configuration of the in-vehicle type fault diagnosis device realized by the ECU 10. Hereinafter, according to FIG. 2, the part which functions as a vehicle-mounted type fault diagnosis apparatus among ECU10 is demonstrated concretely. In FIG. 2, the ECU 10 includes an abnormality detection unit 11, a diagnosis code storage unit 12, an abnormal component estimation table storage unit 13, an abnormal component identification unit 14, an abnormal component data storage unit 15, and an interface unit 16.

  The abnormality detection unit 11 detects various abnormalities in the vehicle based on output signals of various sensors provided in the vehicle 1 and specifies a diagnosis code corresponding to the detected abnormality content.

  The diagnostic code storage unit 12 stores the diagnostic code detected by the abnormality detection unit 11.

  The abnormal part estimation table storage unit 13 includes a combination of diag codes formed by combining a plurality of diag codes, and an abnormal part that is estimated as a cause when a plurality of diag codes included in the combination are detected simultaneously. Is stored in advance. Here, the abnormal part estimation table can be created by an appropriate method. For example, in the design stage, FTA (Fault Tree Analysis), market performance, factor analysis, unit configuration, and part function It is created based on the design developer's rules of thumb. The abnormal part estimation table will be described in detail later with a specific example.

  The abnormal component specifying unit 14 is estimated as the cause based on the abnormal component estimation table stored in the abnormal component estimation table storage unit 13 when a plurality of diagnostic codes are detected simultaneously by the abnormality detection unit 11. Identify abnormal parts. Note that the above "simultaneous" does not mean the same time, and it goes without saying that there may be a time difference in detecting a plurality of diagnostic codes.

  The abnormal part data storage unit 15 stores abnormal part data indicating the abnormal part specified by the abnormal part specifying unit 14.

  In response to a data output request from the failure diagnosis tool 3, the interface unit 16 diagnoses the diagnosis code stored in the diagnosis code storage unit 12 and the abnormal part data stored in the abnormal part data storage unit 15. Output to Tool 3.

  In the above configuration, the abnormality detection unit 11, the abnormal component identification unit 14, and the interface unit 16 are realized by, for example, a CPU executing a predetermined program stored in a storage medium such as a ROM. The diagnostic code storage unit 12 and the abnormal part data storage unit 15 are realized by, for example, a nonvolatile memory such as an EEPROM or a battery-backed RAM. The abnormal part estimation table storage unit 13 is realized by a nonvolatile memory such as a ROM or an EEPROM, for example. However, specific implementation modes of the functional blocks 11 to 16 are not particularly limited.

  In the above configuration, the diagnostic code stored in the diagnostic code storage unit 12 and the abnormal component data stored in the abnormal component data storage unit 15 are erased at an appropriate timing by an appropriate method. For example, after the repair of the vehicle 1 is completed, the interface unit 16 stores the diagnostic code stored in the diagnostic code storage unit 12 and the abnormal part data storage unit 15 in response to a data erasure request from the failure diagnosis tool 3. Erase abnormal part data.

  FIG. 3 is a diagram illustrating an example of the abnormal part estimation table. FIG. 4 is a diagram showing various sensors provided in the vehicle 1 and their wiring. FIG. 5 is a diagram showing a schematic configuration of the motor system 50 of the vehicle 1. Hereinafter, the abnormal part estimation table will be specifically described with reference to FIGS.

  As shown in FIG. 3, the abnormal part estimation table is formed by associating a combination of diag codes (hereinafter referred to as “diag generation pattern”) and an abnormal part name. Here, the abnormal part name is abnormal part data indicating an abnormal part estimated as a cause when a corresponding diagnosis occurrence pattern occurs. In FIG. 3, the abnormal part estimation table is NO. 1-NO. A pair of 100 diagnosis occurrence patterns and abnormal part names, that is, NO. 1-NO. It is composed of 100 records. However, the number of records in the abnormal part estimation table is not particularly limited.

  Here, the NO. One record will be described with reference to FIG. In FIG. 4, the vehicle 1 is provided with sensors 41A, 41B, and 41C. The sensors 41A, 41B, 41C are connected to the connector 43 via signal lines 42A, 42B, 42C, respectively. This connector 43 is connected to the ECU 10 via a signal line 44. The ECU 10 receives output signals from the sensors 41A, 41B, and 41C via the wiring, and executes various processes such as engine control based on the output signals.

  In the above configuration, when the wiring between the sensor 41A and the ECU 10 is disconnected, the ECU 10 detects the disconnection of the wiring of the sensor 41A based on the signal of the input terminal to which the output signal of the sensor 41A is input, and the disconnection The diag code P11 indicating is specified. Similarly, when the wiring between the sensor 41B and the ECU 10 is disconnected, the ECU 10 detects a diagnosis code P12 indicating the disconnection of the wiring of the sensor 41B. Further, when the wiring between the sensor 41C and the ECU 10 is disconnected, the ECU 10 detects a diagnosis code P13 indicating the disconnection of the wiring of the sensor 41C.

  When the diagnosis codes P11, P12, and P13 are detected at the same time by the ECU 10, in view of the configuration of the wiring, the cause is an abnormality of the connector 43 in which the wiring of the sensors 41A, 41B, and 41C is concentrated (connector disconnection, breakage, etc.) ).

  Therefore, as shown in FIG. In the record of 1, the diagnosis occurrence pattern “P11, P12, P13” and the abnormal part name “connector 43” are associated with each other.

  Next, the NO. A few records will be described with reference to FIG. In FIG. 5, the motor system 50 includes a motor 51. The driving power for the motor 51 is supplied from the battery 52 via the inverter 53. Specifically, the direct current output of the battery 52 is converted into a three-phase alternating current by the inverter 53 and supplied to the U, V, and W phase windings of the motor 51.

  The motor 51 is provided with a resolver (rotor angle sensor) 54 that detects the rotation angle of the rotor of the motor 51. A current sensor 55 that detects a current supplied from the inverter 53 to the motor 51 is provided between the inverter 53 and the motor 51. Output signals from the resolver 54 and the current sensor 55 are input to the ECU 10. The ECU 10 controls the inverter 53 based on the output signals of the resolver 54 and the current sensor 55, and controls the current supplied to the motor 51.

  Further, a leakage detector 56 that detects a leakage of the motor 51 on the input side of the inverter 53 is provided between the battery 52 and the inverter 53. A temperature sensor 57 that detects the temperature of the motor 51 is installed in the vicinity of the motor 51. Output signals from the leakage detector 56 and the temperature sensor 57 are also input to the ECU 10.

  In the above configuration, it is assumed that the detection error of the resolver 54 becomes excessive. In this case, the ECU 10 detects an abnormality of the resolver 54 based on the result of the operation check of the resolver 54 alone, and specifies a diagnosis code P21 indicating the abnormality. Further, due to the abnormality of the resolver 54, the current control of the inverter 53 by the ECU 10 is out of order, and the current value detected by the current sensor 55 becomes excessive. In this case, the ECU 10 detects the overcurrent state of the inverter 53 based on the output signal of the current sensor 55, and specifies the diagnosis code P22 indicating the overcurrent state. That is, when the resolver 54 fails and its detection error becomes excessive, it is considered that the diagnostic codes P21 and P22 are detected. On the contrary, when the diagnosis codes P21 and P22 are detected at the same time, an excessive detection error of the resolver 54 is estimated as the cause.

  Therefore, as shown in FIG. In the record of 2, the diagnosis occurrence pattern “P21, P22” and the abnormal part name “resolver 54” are associated with each other.

  Next, in the above configuration, it is assumed that a short circuit between the windings of the motor 51 occurs. In this case, the resistance between the input terminals of the inverter 53 decreases, and the ECU 10 detects a leakage based on the output signal of the leakage detector 56 and specifies the diagnosis code P31 indicating the leakage. Further, the current flowing through the inverter 53 becomes excessive, and the ECU 10 detects the overcurrent state of the inverter 53 based on the output signal of the current sensor 55 and specifies the diagnosis code P22 indicating the overcurrent state. Further, the motor 51 becomes overheated, the temperature detected by the temperature sensor 57 becomes excessive, and the ECU 10 detects an output abnormality of the temperature sensor 57 based on the output signal of the temperature sensor 57, and displays a diagnosis code P32 indicating the abnormality. Identify. That is, when a short circuit occurs between the windings of the motor 51, it is considered that the diagnosis codes P31, P22, and P32 are detected. Conversely, when the diagnosis codes P31, P22, and P32 are detected at the same time, a short circuit between the windings of the motor 51 is estimated as the cause.

  Therefore, as shown in FIG. In the record 3, the diagnosis occurrence pattern “P31, P22, P32” and the abnormal part name “motor 51” are associated with each other.

  Hereinafter, among the operations of the ECU 10, the operation as the in-vehicle type failure diagnosis device will be specifically described by dividing into the operation of the abnormality detection unit 11, the operation of the abnormal component identification unit 14, and the operation of the interface unit 16. It is assumed that the abnormal part estimation table storage unit 13 stores in advance the abnormal part estimation table shown in FIG.

  FIG. 6 is a flowchart showing an operation procedure of the abnormality detection unit 11. The abnormality detection unit 11 monitors output signals from various sensors of the vehicle 1 such as the sensors 41A, 41B, 41C, the resolver 54, the current sensor 55, the leakage detector 56, the temperature sensor 57, and the like. Based on the predetermined abnormality determination conditions, the presence / absence of various abnormalities is determined (S11). For example, the abnormality detection unit 11 acquires the output signal of the resolver 54, and calculates an error in the detection angle from this output signal. The abnormality detection unit 11 determines that the resolver 54 is abnormal when the calculated error is equal to or greater than a predetermined amount, and determines that the resolver 54 is normal when the calculated error is less than the predetermined amount. . This determination is repeatedly performed until some abnormality is detected (S11: NO).

  When a certain abnormality is detected as a result of the determination (S11: YES), the abnormality detection unit 11 identifies a diagnosis code corresponding to the detected abnormality (S12), and the identified diagnosis code is stored in the diagnosis code storage unit 12. (S13). For example, when it is determined that the resolver 54 is abnormal, that is, when an abnormality of the resolver 54 is detected, the abnormality detection unit 11 stores a diag code P21 corresponding to the abnormality of the resolver 54 in the diag code storage unit 12.

  The abnormality detection unit 11 repeatedly executes the processes from steps S11 to S13.

  FIG. 7 is a flowchart showing an operation procedure of the abnormal part specifying unit 14. The process shown in FIG. 7 is the NO. Registered in the abnormal part estimation table. 1-NO. Each of the 100 records is executed sequentially.

  In the processing of a record, the abnormal part specifying unit 14 reads the diagnosis occurrence pattern related to the record from the abnormal part estimation table storage unit 13 (S21). For example, NO. In the processing of the record of No. 1, the abnormal part specifying unit 14 determines that NO. The diagnosis generation pattern “P11, P12, P13” relating to one record is read out.

  Next, the abnormal part specifying unit 14 determines whether or not the read diagnosis occurrence pattern has occurred (S22). Specifically, the abnormal part specifying unit 14 determines whether or not all the diagnosis codes included in the diagnosis occurrence pattern are stored in the diagnosis code storage unit 12. For example, NO. In the processing of the record 1, the abnormal part specifying unit 14 determines that the diagnosis occurrence pattern has occurred when the diagnosis codes P11, P12, and P13 are stored in the diagnosis code storage unit 12, and if not, It is determined that the diagnosis occurrence pattern has not occurred.

  If it is determined that the diagnosis occurrence pattern has not occurred (S22: NO), the process returns to step S21, and the abnormal part specifying unit 14 processes the next record.

  On the other hand, when it is determined that the diagnosis occurrence pattern has occurred (S22: YES), the abnormal component specifying unit 14 refers to the abnormal component estimation table and selects the abnormal component name associated with the diagnosis occurrence pattern. The specified abnormal part name is written into the abnormal part data storage unit 15 (S24). For example, NO. In the processing of the record of No. 1, the abnormal part specifying unit 14 determines that NO. The abnormal part name “connector 43” related to the record 1 is read and stored in the abnormal part data storage unit 15.

  Then, when the abnormal part name storing process is completed, the process returns to step S21, and the abnormal part specifying unit 14 processes the next record.

  Note that the processing shown in FIG. 7 can be executed at an appropriate timing. For example, the ECU 10 may be repeatedly executed continuously during the ON state, or may be periodically executed. Moreover, it may be performed according to an instruction operation input via an appropriate user interface.

  FIG. 8 is a flowchart showing an operation procedure when the interface unit 16 outputs data. In FIG. 8, the interface unit 16 stands by until it receives a data output request from the failure diagnosis tool 3 (S31: NO). When the interface unit 16 receives a data output request from the failure diagnosis tool 3 (S31: YES), the interface unit 16 reads all the diag codes stored in the diag code storage unit 12 (S32). Is transmitted to the failure diagnosis tool 3 (S33). Further, the interface unit 16 reads all abnormal component names stored in the abnormal component data storage unit 15 (S34), and transmits all the read abnormal component names to the failure diagnosis tool 3 (S35). Thus, the diagnosis code and the abnormal part name output to the failure diagnosis tool 3 are displayed on the display of the failure diagnosis tool 3. For example, the abnormal part name “connector 43” is displayed together with the diagnosis codes P11, P12, and P13.

  As described above, the in-vehicle type fault diagnosis apparatus according to the present embodiment includes a combination of diagnostic codes and an abnormal component that is estimated as a cause when a plurality of diagnostic codes included in the combination are detected at the same time. The associated abnormal part estimation table is stored in advance, and when a plurality of diagnostic codes are detected simultaneously, the abnormal part estimated as the cause is specified based on the abnormal part estimation table. For this reason, according to the present embodiment, maintenance and repair of the vehicle can be facilitated. Specifically, it is possible to avoid a situation where it takes a very long time to identify an abnormal part at the service site or a situation where all parts related to a plurality of diagnostic codes are replaced. For example, when a plurality of diagnostic codes P11, P12, and P13 are generated, an abnormal part “connector 43” estimated to be the cause is displayed on the failure diagnosis tool 3 together with these diagnostic codes. The cause of the diagnostic code can be easily grasped, and the connector 43 can be confirmed, repaired, or replaced.

  In addition, this invention is not limited to the said embodiment, It can change variously within the range which does not deviate from the summary of this invention.

  For example, the diagnosis code and abnormal part data are output to the failure diagnosis tool 3 in the above embodiment, but may be output to other devices. For example, it may be output to an output device (display or the like) inside the vehicle, or may be transmitted to a management server outside the vehicle via a wireless communication line.

  In the above embodiment, for convenience of explanation, one ECU 10 is shown, but the function of this ECU 10 may be realized by a plurality of ECUs connected to each other via an in-vehicle network.

  In the above embodiment, an abnormal part is specified when all the diagnosis codes included in the diagnosis generation pattern are stored in the diagnosis code storage unit 12, but a plurality of diagnosis codes included in the diagnosis generation pattern are identified. An abnormal part may be specified when a predetermined number or more of codes are stored in the diagnosis code storage unit 12.

  The on-vehicle failure diagnosis apparatus may output the abnormal part data to the outside in association with a plurality of diagnosis codes corresponding to the abnormal part data. With such a configuration, it is easy to grasp the correspondence between abnormal part data and a diagnosis code, and it is possible to further facilitate maintenance and repair.

1 is a schematic diagram showing a schematic configuration of a failure diagnosis system including an in-vehicle failure diagnosis apparatus according to an embodiment. It is a block diagram which shows the function structure of the vehicle-mounted type failure diagnosis apparatus implement | achieved by ECU. It is a figure which shows an example of an abnormal component estimation table. It is a figure which shows the various sensors provided in the vehicle, and its wiring. It is a figure which shows schematic structure of the motor system of a vehicle. It is a flowchart which shows the operation | movement procedure of an abnormality detection part. It is a flowchart which shows the operation | movement procedure of an abnormal component specific part. It is a flowchart which shows the operation | movement procedure at the time of the data output of an interface part.

Explanation of symbols

  DESCRIPTION OF SYMBOLS 1 Vehicle, 3 Failure diagnosis tool, 10 ECU, 11 Abnormality detection part, 12 Diag code memory | storage part, 13 Abnormal part estimation table memory | storage part, 14 Abnormal part specific | specification part, 15 Abnormal part data storage part, 16 Interface part

Claims (2)

In the vehicle-mounted fault diagnosis device that detects various abnormalities in the vehicle as diag codes indicating the abnormal contents,
Table storage means for storing in advance an abnormal component estimation table in which a combination of diagnostic codes and an abnormal component estimated as a cause when a plurality of diagnostic codes included in the combination are detected at the same time;
When a plurality of diagnostic codes are detected at the same time, based on the abnormal part estimation table stored in the table storage means, an abnormal part specifying means for specifying an abnormal part estimated as the cause;
An on-vehicle type fault diagnosis device characterized by comprising: In the on-vehicle type fault diagnosis device according to claim 1,
Abnormal part data storage means for storing abnormal part data indicating the abnormal part specified by the abnormal part specifying means;
In response to a request from a failure diagnosis tool outside the vehicle, abnormal component data output means for outputting abnormal component data stored in the abnormal component data storage means to the failure diagnosis tool;
An on-vehicle type fault diagnosis device characterized by comprising:

Images