JP6766612B2 - In-vehicle fault diagnosis device - Google Patents

Description

The present invention relates to a failure diagnosis device mounted on a vehicle and performing a failure diagnosis of an in-vehicle device.

The vehicle is equipped with an ECU (Electric Control Unit). The ECU controls various devices mounted on the vehicle, performs failure diagnosis, and the like. Failure diagnosis processing such as failure detection, determination, notification, and recording is processed in the ECU of each device such as a brake.

In recent years, a series of standards called OBDII (On Board Diagnostics) have been presented as standards for vehicle failure diagnosis. Patent Document 1 analyzes the failure state based on the diagnostic code from the device corresponding to the OBDII standard and the operation state at the time of failure, ranks the failure state according to the seriousness of the failure, and displays the display method corresponding to the rank. -Disclosures a failure diagnosis system that displays by content. Further, Patent Document 2 discloses a vehicle diagnostic system in which a transponder is provided in a vehicle diagnostic system corresponding to the OBDII standard to make the vehicle diagnostic system compatible with the OBDII standard having wireless communication requirements.

Japanese Unexamined Patent Publication No. 2003-22330 Japanese Unexamined Patent Publication No. 2006-177769

The failure diagnosis of the regenerative cooperative brake is performed by the regenerative cooperative brake ECU, but the method does not conform to the OBDII standard. However, the OBDII standard compliance (legal regulation) of the exhaust gas countermeasure device is progressing, and the regenerative cooperative brake ECU is also required to promptly comply with the OBDII standard.

The present invention has been made in view of the above problems, and an object of the present invention is to provide a failure diagnosis device corresponding to the OBDII standard by a simple method.

In order to solve the above problems, one aspect of the present invention is a failure diagnosis device mounted on a vehicle and performing a failure diagnosis of a predetermined device, and obtains information indicating an operating state of the device, and the first aspect thereof. Whether or not the device is in an abnormal state based on the first failure detection means that performs the failure detection process of the device based on the detection criteria, the failure detection process result of the first failure detection means, and the first determination criterion. A first abnormality that outputs an abnormality notification instruction to the first abnormality notification means, which is a brake warning light, based on the abnormality determination processing result of the first abnormality determination means that performs the abnormality determination processing for confirming the determination and the first abnormality determination means. A second failure detection means that acquires information indicating the operation status of the output means and the device and performs failure detection processing of the device based on this and the OBDII (On Board Diagnostics) standard, and a failure detection of the second failure detection means. Based on the processing result and the second abnormality determination means that performs abnormality determination processing for determining whether or not the device is in an abnormal state based on the OBDII standard, and the abnormality determination processing result of the second abnormality determination means, OBDII It is provided with a second abnormality output means that outputs an abnormality notification instruction to the second abnormality notification means, which is a failure warning light of the abnormality notification method that corresponds to the standard and is independent of the abnormality notification method of the first abnormality output means. In this way, by additionally providing a failure diagnosis function corresponding to the OBDII standard to the conventional failure diagnosis device, it is possible to make the failure diagnosis device compatible with the OBDII standard by a simple method without modifying the conventional part. it can. In addition, since the added part and the conventional part are highly independent, there is no effect on the warning display and fail-safe function by the conventional method, and even if the OBDII standard is supported, the discomfort given to the user can be reduced. In addition, it is easy to grasp the correction range for the specification change, and the correction can be facilitated.

According to the present invention, it is possible to provide a failure diagnosis device corresponding to the OBDII standard by a simple method.

The figure which shows the module structure of the ECU program which concerns on a prior art example. Functional block diagram as a failure diagnosis device of the ECU according to the conventional example Sequence diagram of failure diagnosis processing according to the conventional example The figure which shows the module structure of the ECU program which concerns on one Embodiment of this invention. Functional block diagram of an ECU as a failure diagnosis device according to an embodiment of the present invention. Sequence diagram of failure diagnosis processing according to one embodiment of the present invention

(Overview)
The present invention is a failure diagnosis device that is mounted on a vehicle and performs failure diagnosis of a predetermined device such as a regenerative cooperative brake. The failure diagnosis device includes each means for performing failure detection, abnormality determination, etc. by a conventional method, and each means for performing failure detection, abnormality determination, etc. based on the OBDII standard. Such a failure diagnosis device can be easily configured by adding a function corresponding to the OBDII standard to the conventional failure diagnosis device. In addition, since the added means and the conventional means are highly independent, the interface of the conventional brake is not affected and there is little discomfort to the user, and it is easy to grasp the correction range when the specifications are changed.

(Conventional example)
Prior to the description of the embodiment of the present invention, the regenerative cooperative brake ECU of the prior art will be described. FIG. 1 is a module structure diagram of a program executed by the processor of the regenerative cooperative brake ECU according to a conventional example. The module group is classified into each layer of APP (application) 910, AFW (application framework) 920, PF (platform) 930, and each group of ECU management unit 940. Each group contains one or more modules (APP_1, ..., APP_L, AFW_1, ..., AFW_M, PF_1, ..., PF_N, ECU_1, ..., ECU_P).

The module of PF930 performs processing depending on each device constituting the regenerative cooperative brake. For example, changes in specifications such as changes in sensor characteristics are supported by changing the modules in this layer. The module of AFW920 performs processing depending on the configuration of the regenerative cooperative brake and generation of information commonly used by APP910. For example, specification changes such as changes in tire diameter and brake lever ratio can be handled by changing the modules in this layer. The APP910 module provides services to users such as VDM (Vehicle Dynamics Management) and brake-by-wire control. For example, the difference in service depending on the vehicle type can be dealt with by changing the module of this layer. The module of the ECU management unit 940 collects, stores, and outputs control information and failure information from each layer, and makes a final determination of abnormality and a decision to implement fail-safe measures based on the failure information.

FIG. 2 shows an example of a functional block as a failure diagnosis device 900 of the regenerative cooperative brake ECU. The failure diagnosis device 900 includes a failure detection means 950, an abnormality determination means 960, and an abnormality output means 970, and is connected to the regenerative cooperative brake 200 and the first abnormality notification means 300. FIG. 3 shows an example of the sequence at the time of executing the failure diagnosis of the failure diagnosis device 900.

[Step S91]: The failure detecting means 950 is realized by a part of the modules of the above-mentioned PF930 and AFW920, and obtains information indicating the operating state of each device constituting the regenerative cooperative brake 200 from, for example, a sensor, and obtains information from the sensor or the like. A failure is detected based on a predetermined detection criterion (first detection criterion). For example, if the numerical value indicating the operating state of a certain device deviates from a predetermined range, it is detected as a device failure, and if it does not deviate, it is detected as normal. The detection result is represented by, for example, setting a flag corresponding to the detected failure, and is notified to the abnormality determining means 960.

[Step S92]: The abnormality determination means 960 is realized by a part of the module of the ECU management unit 940, and regenerates based on the failure detection result of the failure detection means 950 and a predetermined determination criterion (first determination criterion). A comprehensive judgment is made as to whether or not the cooperative brake ECU is in an abnormal state. For example, when the failure state of a predetermined device is continuously detected for a certain period of time or longer, it is determined that the regenerative cooperative brake is in an abnormal state in which the normal function cannot be exhibited. However, for example, if the failure state is resolved within a certain period of time, it is not determined to be an abnormal state. The determination result is represented, for example, by setting a flag corresponding to the detected abnormality, and is notified to the abnormality output means 970.

[Step S93]: The abnormality output means 970 is realized by a part of the module of the ECU management unit 940, and if the determination result of the abnormality determination means 960 is determined to be an abnormality, the abnormality notification instruction is output.

[Step S94]: The first abnormality notification means 300 is an external device connected to the failure diagnosis device 900, and when the abnormality output means 970 receives an abnormality notification instruction, a predetermined abnormality notification method (first). Anomaly notification method) is used for notification. The predetermined abnormality notification method is, for example, a method of notifying an abnormality by turning on a brake warning light.

Hereinafter, an embodiment of the present invention will be described in detail with reference to the drawings.

(Constitution)
FIG. 4 is a modular structure of a program executed by the processor of the regenerative cooperative brake ECU according to the present embodiment. Similar to the conventional example described above, the module group is classified into each layer of APP (application) 110, AFW (application framework) 120, PF (platform) 130, and each group of ECU management unit 140. Each group contains one or more modules (APP_1, ..., APP_L, AFW_1, ..., AFW_M, PF_1, ..., PF_N, ECU_1, ..., ECU_P, ECU_O). The module structure of the present embodiment can be configured by adding a process corresponding to the OBDII standard to the module of the above-mentioned conventional example. In FIG. 4, a portion added to the conventional portion, which is a portion included in the conventional example, is schematically displayed by hatching.

Some of the modules of the PF130 and AFW120 will have additional processing corresponding to the OBDII standard. The processing to be added is mainly the definition of failures and abnormalities based on the OBDII standard and the detection / judgment processing thereof. Further, the AFW120 module is added with a process of outputting an abnormality notification instruction to the abnormality notification means corresponding to the abnormality notification method corresponding to the OBDII standard. A new module ECU_O is added to the ECU management unit 140. The module ECU_O performs an abnormality determination process corresponding to the OBDII standard described later, and a process related to communication such as data storage / erasure and data reading from the outside corresponding to the OBDII standard.

FIG. 5 shows a functional block of the regenerative cooperative brake ECU as a failure diagnosis device 100. The failure diagnosis device 100 includes a first failure detection means 150, a first abnormality determination means 160, a first abnormality output means 170, a second failure detection means 151, a second abnormality determination means 161 and a second abnormality output means 171. The regenerative cooperative brake 200 is connected to the first abnormality notification means 300 and the second abnormality notification means 301.

(processing)
FIG. 6 shows a sequence when the failure diagnosis of the failure diagnosis device 100 is executed. The following processes in steps S11-S14 and steps S15-S18 are not limited in execution timing and can be executed in parallel without depending on each other. Further, these processes can be executed repeatedly at all times, and are always executed, for example, while the vehicle is running. It should be noted that the sequence is an example schematically shown, and does not limit the specific implementation form of each functional block.

[Step S11]: The first failure detecting means 150 is realized by the conventional parts of the modules of the above-mentioned PF130 and AFW120, and like the failure detecting means 950 of the conventional example, the first failure detecting means 150 of each device acquired from the sensor of the regenerative cooperative brake 200 or the like. A failure is detected based on information indicating an operating state and a conventional predetermined detection standard (first detection standard).

[Step S12]: The first abnormality determination means 160 is realized by the conventional portion of the module of the ECU management unit 140, and like the abnormality determination means 960 of the conventional example, the failure detection result by the first failure detection means 150 and the conventional predetermined value. Judgment as to whether or not the regenerative cooperative brake is in an abnormal state is performed based on the determination criteria (first determination criteria) of.

[Step S13]: The first abnormality output means 170 is realized by the conventional portion of the module of the ECU management unit 140, and when it is determined that the first abnormality determination means 160 is in an abnormal state, the first abnormality notification means 300 is used. Outputs an error notification instruction.

[Step S14]: The first abnormality notification means 300 is an external device connected to the failure diagnosis device 100, and when the abnormality notification instruction output by the first abnormality output means 170 is received, a conventional predetermined abnormality notification method is used. For example, the brake warning light is lit according to the (first abnormality notification method).

[Step S15]: The second failure detecting means 151 is realized by the additional parts of the modules of the above-mentioned PF130 and AFW120, and information indicating the operating state of each device constituting the regenerative cooperative brake is obtained from the sensor of the regenerative cooperative brake 200 or the like. Acquire and detect the failure based on this and the detection criteria of the OBDII standard. The detection result is represented by, for example, setting a flag corresponding to the detected failure, and is notified to the second abnormality determining means 161.

[Step S16]: The second abnormality determination means 161 is realized by the module ECU_O which is an additional part of the ECU management unit 140, and is regeneratively coordinated based on the detection result of the second failure detection means 151 and the determination standard of the OBDII standard. A comprehensive judgment is made as to whether or not the brake ECU is in an abnormal state. The determination result is represented by, for example, setting a flag corresponding to the detected abnormality, and is notified to the second abnormality output means 171.

[Step S17]: The second abnormality output means 171 is realized by the module ECU_O which is an additional part of the ECU management unit 140, and when it is determined that the second abnormality determination means 161 is in an abnormal state, an abnormality notification instruction is output. To do.

[Step S18]: The second abnormality notification means 301 is an external device connected to the failure diagnosis device 100 in order to comply with the OBDII standard, and when the second abnormality output means 171 receives the abnormality notification instruction output, the OBDII Performs notification corresponding to the abnormality notification method corresponding to the standard. The abnormality notification method corresponding to the OBDII standard is, for example, a method of notifying an abnormality by turning on a MIL (Malfunction Indication Lamp).

(effect)
In the present invention, the regenerative cooperative brake ECU that performs failure detection, abnormality determination, abnormality notification, and fail-safe measures by the conventional method is not changed to the conventional method, but fails detection and abnormality corresponding to the OBDII standard. Since the functions of judgment and abnormality notification are added, existing software assets can be utilized and easily made compatible with the OBDII standard.

Further, since the processing of the additional part for complying with the OBDII standard is realized as a functional block or sequence independent of the conventional part, it can be made independent of the processing such as abnormality notification and fail-safe by the conventional method. Therefore, even if the OBDII standard is supported, the user interface of the conventional part is not changed, and the discomfort given to the user can be reduced. For example, it is possible to only add the MIL display specification according to the OBDII standard without changing the display specification of the conventional brake warning light. In addition, since there is no influence of the OBDII standard compliant part on the fail-safe function performed by the conventional method, it is easy to verify the safety. In addition, it is possible to easily grasp the correction range for responding to any specification change of both the OBDII standard and the regenerative cooperative brake, and facilitate future correction.

(Modification example)
In the present embodiment, as an example, the case where the regenerative cooperative brake is made to correspond to the OBDII standard has been described, but the present invention can also be applied to the correspondence to the OBDII standard of other devices mounted on the vehicle. That is, to the software of the existing ECU that controls the device, the definitions of failures and abnormalities newly required by the OBDII standard, their detection / judgment processing, and the data management function are appropriately added, and the ECU, MIL, etc. , The abnormality notification means that requires a new connection may be connected by CAN or the like. In addition, the OBDII standard is not limited to a specific version, and may include current and future updated versions and derivative versions. In the above description, each functional block of the failure diagnosis device is realized by software, but even if at least a part of the functional blocks are realized by hardware, the present invention is applied to achieve the same effect. Obtainable.

The present invention is useful for ECU devices and the like mounted on vehicles.

100 Failure diagnosis device 150 1st failure detection means 151 2nd failure detection means 160 1st abnormality determination means 161 2nd abnormality determination means 170 1st abnormality output means 171 2nd abnormality output means 200 regenerative cooperative brake 300 1st abnormality notification means 301 Second abnormality notification means 900 Failure diagnosis device 950 Failure detection means 960 Abnormality determination means 970 Abnormality output means

Claims (1)

It is a failure diagnosis device that is mounted on a vehicle and performs failure diagnosis of a predetermined device.
A first failure detection means that acquires information indicating an operating state of the device and performs a failure detection process of the device based on this and a first detection criterion.
A first abnormality determination means that performs an abnormality determination process for determining whether or not the device is in an abnormal state based on the failure detection processing result of the first failure detection means and the first determination criterion.
Based on the abnormality determination processing result of the first abnormality determination means, the first abnormality output means that outputs an abnormality notification instruction to the first abnormality notification means that is a brake warning light, and
A second failure detection means that acquires information indicating the operating state of the device and performs failure detection processing of the device based on this and an OBDII (On Board Diagnostics) standard.
A second abnormality determination means that performs an abnormality determination process for determining whether or not the device is in an abnormal state based on the failure detection processing result of the second failure detection means and the OBDII standard.
Based on the abnormality determination processing result of the second abnormality determination means, the second abnormality notification means which is a failure warning light of the abnormality notification method corresponding to the OBDII standard and independent of the abnormality notification method of the first abnormality output means. A failure diagnosis device including a second abnormality output means for outputting an abnormality notification instruction.

Images