JP2003027981A - Vehicular failure diagnostic system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a vehicular failure diagnostic system that can easily specify a cause of the failure. SOLUTION: The vehicular failure diagnostic system has a first electronic control unit 1 and second electronic control units 2 connected for data transmission and reception via a communication line 3, in which the first electronic control unit has a clock 14 with a calendar function, and each second electronic control unit acquires and stores date/time data clocked by the clock via the communication line upon failure occurrence detection. Failure display by a failure diagnostic tester uses the date/time data to show a failure occurrence sequence of individual failure points about each electronic control unit, so that the cause of the failure is easily specified.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a vehicle failure diagnosis apparatus for displaying a failure state based on failure data stored in an electronic control unit.

[0002]

2. Related Background Art Generally, a vehicle is equipped with various electronic control units for engine control, shift control, suspension control, brake control, etc., and the electronic control units can exchange data with each other via multiple transmission paths. It is connected to the. Further, each electronic control unit is provided so as to be able to detect the failure of the sensors and actuators connected to it and the failure of the electronic control unit itself, and stores a failure code that specifies the location where the failure has occurred at the time of failure detection and an alarm signal. Is supposed to occur.

Then, when the driver brings the vehicle to a maintenance shop according to an alarm such as lighting of an alarm lamp in response to an alarm signal, a failure diagnostic tester is connected to the electronic control unit and is sent from the failure diagnostic tester to each electronic control unit. Each electronic control unit sends the failure data to the failure diagnostic tester in response to the failure data sending command, and the failure code indicating the failure point is displayed on the display screen of the failure diagnostic tester based on the failure data. Use the failure code as a clue to identify the location of the failure and perform inspection and repair.

[0004]

However, it may be difficult to specify the cause of failure based on only the failure code display. In this case, the repair shop requires time and labor to inspect and repair the vehicle. Also, the cost burden on the user side increases. Therefore, an object of the present invention is to provide a vehicle failure diagnosis device that can easily identify the cause of a failure.

[0005]

A vehicle failure diagnosis apparatus according to a first aspect of the present invention can detect a failure occurrence order based on an electronic control apparatus capable of storing failure data and the failure data stored in the electronic control apparatus. Thus, a failure diagnosis means capable of displaying a failure state is provided. In the failure diagnosing device according to the first aspect, the failure data may include a failure code representing a failure location, and the failure status is displayed so that the failure diagnosing means can understand the failure occurrence order based on such failure data. That is, according to the conventional method, since only the failure occurrence portion is specified, it is difficult to grasp the relationship between the failure portions when failures occur at a plurality of locations related to one electronic control device, and the failure occurrence occurs. Although this is one of the reasons why it is difficult to identify the cause, according to the present invention, the order of failure occurrence can be easily confirmed based on the failure status display of the failure diagnosis means. For this reason, the location of the first failure, the order of subsequent failures, the intervals between occurrences, and the relationships between the failure locations can be understood, making it easier to identify the cause of failure and the burden required to inspect and repair the failure location at the maintenance shop. And the cost burden on the user side is reduced accordingly.

According to another aspect of the failure diagnosis device of the present invention, the electronic control device stores the failure data in the order of occurrence, and the failure diagnosis means displays the failure state in the order of storage of the failure data in the electronic control device. According to this preferred aspect, the failure data is stored in the electronic control unit in the order of failure occurrence, and the failure status is displayed by the failure diagnosis means in the order of storage,
Failure status display is performed so that the failure occurrence order can be understood.
In other words, by performing the failure status display according to the above-mentioned data storage / display procedure, it is possible to include information indicating the failure occurrence order in the failure status display. In addition, no special data writing procedure is required when failure data is stored in the order of failure occurrence, and no special data read / display procedure is required for failure status display according to the failure data storage order. That is, according to the failure diagnosis device of the second aspect, it is possible to easily realize the failure state display so that the failure occurrence order can be understood.

According to another aspect of the failure diagnosing device of the present invention, a plurality of electronic control devices including the first and second electronic control devices are connected to each other by a communication network means so that information can be transmitted between them.
The first electronic control unit has a time measuring unit, and the second electronic control unit acquires and stores the time measured value measured by the time measuring unit via the communication network unit when detecting the occurrence of a failure. Then, the failure state displayed by the failure diagnosing means includes the time value.

According to this preferred aspect, the failure status display includes a time value indicating the failure occurrence time. For example, when failures occur at a plurality of locations, the failure occurrence time at each failure location is displayed when the failure status is displayed. Each is displayed, and the failure occurrence order is clearly displayed. Further, the number of the first electronic control devices provided with the time measuring means may be one, and in this case, the cost of the failure diagnosing device can be reduced by sharing one time measuring means with a plurality of electronic control devices.

According to another aspect of the failure diagnosis apparatus of the present invention, the time measuring means is composed of a clock means capable of determining the date and time.
According to this preferable aspect, the date and time when the failure occurs can be included in the failure state display, and the failure occurrence date and time as well as the failure occurrence order can be immediately confirmed, and the cause of the failure occurrence can be easily identified.

According to another aspect of the failure diagnosis apparatus of the present invention, the counter means constitutes the time measuring means. According to this preferred mode, in the failure state display, each failure occurrence time point can be displayed numerically by using the counter value, whereby the failure occurrence order can be easily confirmed, so that the failure cause can be easily identified.

According to a sixth aspect of the present invention, there is provided a failure diagnosing device, wherein the counter means provided in each of the plurality of electronic control units is activated when a failure related to each electronic control unit first occurs. According to this preferred aspect, it is not necessary to increment the count value of the counter means of the electronic control device in a predetermined cycle while the failure related to each electronic control device does not occur, and therefore, the operation control of the counter means is unnecessary. The load on the electronic control unit is reduced. Further, each time the occurrence of a failure is detected in each electronic control unit, the count value at the time of failure occurrence can be stored together with the failure code,
Therefore, the failure occurrence order can be indicated by including these count values in the failure status display by the failure diagnosis means.

According to a seventh aspect of the present invention, there is provided the failure diagnosing device, wherein the failure diagnosing means is provided with clock means for specifying a failure occurrence date and time based on the count value of the counter means of each electronic control unit. According to this preferred aspect, the failure diagnosing means can acquire the failure occurrence date and time data from the failure data including the count value and include the failure occurrence date and time in the failure status display, whereby the mechanic can immediately report the failure occurrence date and time. It is easy to confirm and identify the cause of failure. Further, it is not necessary to provide a clock means in each electronic control device, and the device configuration can be simplified accordingly.

According to another aspect of the present invention, there is provided a failure diagnosing device which activates the counter means of each of the plurality of electronic control devices in response to an instruction from the failure diagnosing means. According to this preferred aspect, for example, the counter means of the plurality of electronic control devices can be simultaneously activated at the time of shipment of the vehicle in which the electronic control devices are mounted, and the count value can be detected each time the occurrence of a failure related to each electronic control device is detected. By including the count value in the failure state display of the failure diagnosing means, it is possible to easily grasp the failure occurrence history after the vehicle is shipped, for example, the failure occurrence frequency at each location, the failure occurrence time interval, and the like. In this case, for example, the memory of the failure code is erased after the repair of the failure portion, while the increment of the count value is substantially continuously performed before and after the repair.

[0014]

BEST MODE FOR CARRYING OUT THE INVENTION A vehicle failure diagnosis device according to a first embodiment of the present invention will be described below. Referring to FIG.
The failure diagnosis apparatus according to the present embodiment includes a first electronic control unit, for example, an electronic control unit for controlling an engine (hereinafter, referred to as a first E
CU) 1 and a second electronic control unit, for example, a shift control electronic control unit (hereinafter referred to as a second ECU) 2, and the electronic control units exchange data with each other via a communication line (multiplex transmission line) 3. Connected possible. Although not shown, a plurality of electronic control units (EC
U) is also connected to the communication line 3 so that data can be exchanged between them.

In the multiplex communication system using the vehicle communication line 3, each ECU functions as a communication node and can detect the operating states of the sensors and actuators connected to it, as well as another ECU. It is possible to detect any sensor output or any actuator operating state via the sensor. All ECUs perform integrated control operation according to the vehicle operating state represented by the sensor output or actuator operating state to perform the required vehicle operation. It is supposed to be. In this multiplex communication system, CAN (Co
Vehicle network protocols such as controller area network are used.

More specifically, the first ECU 1 includes a communication line 3
It has a first interface circuit 11 connected to, a communication processing unit 12 connected to it, a CPU 13 connected to this communication processing unit, a clocking unit 14, a memory (storage unit) 15, and the like. The communication line 3, the interface circuit 11, and the communication processing unit 12 constitute a communication network unit that connects a plurality of ECUs so that information can be transmitted.

Sensors and actuators such as a fuel injection valve are connected to the CPU 13 via a second interface circuit 16 (in FIG. 1, reference numeral 17 indicates one of the sensors, and reference numeral 18). Represents one of the actuators The clock means 14 is composed of a clock (clock means) having a calendar function and capable of determining the date and time (clock value).

The first ECU 1 executes a failure diagnosis program (not shown) to detect the presence / absence of a failure of the first ECU 1 itself, sensors and actuators connected to the first ECU 1, and when a failure is detected, a failure code indicating a failure location is provided. The failure occurrence date and time obtained by referring to the clock is written in the memory 15. The second ECU 2 has the same basic configuration as the first ECU 1, but does not include a clock used to identify the date and time of failure occurrence, and when the occurrence of failure is detected, the second ECU 2 is connected to the first ECU 1 via the communication line 3. The failure occurrence date and time is requested to be sent, the failure occurrence date and time calculated by the first ECU 1 with reference to the clock and sent out through the communication line is written in the memory together with the failure code.
Note that other ECUs not shown have the same configuration.

Further, it is not necessary that all of the ECUs constituting the above-mentioned multiplex communication system be provided with sensors and actuators. For example, one of the ECUs is constituted by only the elements 11 to 15 shown in FIG. Alternatively, an ECU dedicated to the clock means 14 may be used as the first electronic control unit. Now, each of the ECUs of the present embodiment individually executes a failure diagnosis and issues an alarm signal when a failure occurrence is detected. However, in the following description, a case where the second ECU 2 fails will be described as an example. To do.

The second ECU 2 periodically executes the failure data storage routine illustrated in FIG. 2 when the ignition key is in the ON state. In this failure data storage routine, a failure diagnosis program is executed to determine whether or not a failure has occurred (step S1),
If the determination result is negative (No), the failure data storage process in this cycle is ended.

On the other hand, when the occurrence of a failure is detected in step S1, the second ECU 2 transmits a date / time data transmission request to the first ECU 1 (step S2), and then the first ECU
It is determined whether the date and time data from 1 has been received (step S3). When receiving the date and time data transmission request, the first ECU
1 acquires the current date and time data, and then the second ECU 2 of the transmission partner from the data frame related to the date and time data transmission request.
And the current date and time data is transmitted to this second ECU 2.

When the current date and time data is received, the second ECU
2 is a failure code indicating a failure point determined by the failure diagnosis processing in step S1 and the first ECU 1 in step S3.
The current date and time data received from the device is written as failure data in the failure data storage area of the memory (step S4).
The failure related to the second ECU 2 occurs in one or more of the ECU itself, the sensors connected to the ECU, and the actuator, and a plurality of failures may occur in a chained relationship with each other. The memory of the present embodiment has a failure data storage area composed of a required number of area parts, and the failure data stored in one or more area parts is erased after inspection and repair related to the failure. Therefore,
The first failure after the last inspection and repair is step S
If it is detected in step 1, the failure data related to the failure is stored in the first failure data storage area portion in step S4.

In the next step S5, the second ECU 2 issues an alarm signal. In response to this alarm signal, for example, an alarm lamp (not shown) on the instrument panel is turned on. FIG. 1 shows a configuration in which the first ECU 1 lights the alarm lamp 19 in response to the alarm signal from the second ECU 2.
As described above, when a failure occurs, the failure data is stored and the alarm is displayed. However, since the routine of FIG. 2 is periodically executed, if a failure occurs at a plurality of locations related to the second ECU 2, these failures will occur. A plurality of pieces of failure data respectively related to are sequentially stored in the failure data storage area of the first and subsequent areas in the order of failure occurrence.

A similar failure data storage routine is executed in the first ECU 1, but since the first ECU 1 has a built-in clock, the routine executed by the first ECU 1 corresponds to steps S2 and S3 in FIG. Does not include the date / time data transmission request / reception procedure. Now, when the driver brings the vehicle to the maintenance shop according to the notification of the failure occurrence due to the lighting of the alarm lamp or the like, the connector of the failure diagnosis tester (fault diagnosis means) 5 is connected to the vehicle side connector 4a connected to the multiplex transmission line in the maintenance shop. 5a is connected. The failure diagnosis tester 5 constitutes the failure diagnosis device of the present embodiment together with the first ECU 1 and the second ECU 2, and based on the failure data (failure code and failure occurrence date) stored in each ECU,
The failure status related to each ECU is displayed on the screen so that the failure occurrence order can be understood for each ECU.

When the ignition key of the vehicle brought into the maintenance shop is in the ON state, the failure data sending routine illustrated in FIG. 3 is executed by each ECU. In this sending routine, the second ECU 2 determines the failure diagnosis tester 5
It is determined whether or not a failure data transmission command has been received from (step S11), and if the same command has not been received, execution of the transmission routine in the current cycle ends.

When the fault data transmission command is received, the second E
The CU 2 reads the failure data from the Nth failure data storage area of the memory (step S12). The initial value of N is "1", and the failure data relating to the failure that first occurred in relation to the second ECU 2 is read from the first failure data storage area portion. Next, it is judged whether or not the transmission of all the failure data is completed after the index N for identifying the storage area portion is incremented by "1" (steps S13 and S14), and if all the data has not been transmitted. In step S12, the failure data relating to the second failure that has occurred is read from the failure data storage area.

When the transmission of the fault data from the second ECU 2 to the fault diagnostic tester 5 is completed as described above, the transmission routine of FIG. 3 is completed. In the fault diagnosis tester 5, FIG.
The failure display routine illustrated in FIG. The failure diagnosis tester 5 of the present embodiment includes a memory having a failure data storage area composed of a required number of failure data storage areas.
The failure data sequentially transmitted from the ECU in the order of failure occurrence is sequentially stored in the first and subsequent failure data storage areas.

In the failure display routine of FIG. 4, the failure diagnosis tester 5 determines whether the failure data has been received from the second ECU 2 (step S21). The initial value of is "1"), and the failure data is read from the failure data storage area portion and analyzed, whereby the failure code and date and time data included in the failure data are extracted (step S2).
2) Next, on the display screen of the failure diagnosis tester 5, a failure display including a failure code and date and time data is displayed (step S23). Next, the index N is incremented by "1" (step S24), and it is determined whether or not the failure display for all data is completed (step S).
25).

If the failure display has not been completed for all data, the procedure from step S22 is executed, whereby E
The failure data is analyzed and displayed in the order of reception from the CU. Then, when the failure display of all the data is completed, the failure display routine is ended. As described above, since the analysis of one or more failure data is executed in the failure data reception order (failure data storage order in the ECU), the failure diagnosis tester 5 displays a failure related to the second ECU 2 on the display screen. The failure codes that specify the points are displayed together with the date and time data in the order of failure occurrence.

In this way, when a failure occurs at a plurality of locations in relation to one ECU, the date and time of failure occurrence at each failure location is displayed, so that the mechanic has a relationship between the failure locations. Can be grasped accurately and easily, and the cause of failure and the location of the failure and the subsequent inspection and repair work can be carried out quickly and accurately. Further, by providing only one ECU (the first ECU 1 in this embodiment) with the timepiece, it is possible to share one timepiece with a plurality of ECUs and reduce the cost of the failure diagnosis device. Also, the first ECU
1. Similar failure diagnosis can be performed for other ECUs (not shown).

A vehicle failure diagnosis device according to a second embodiment of the present invention will be described below. The failure diagnosis apparatus of this embodiment is characterized in that it can be constructed at a lower cost than that of the first embodiment. Therefore, in the failure diagnosis device of the present embodiment, the first ECU 1 includes a counter (not shown) (corresponding to the counter 20 of FIG. 5) instead of the timepiece 14 shown in FIG. It has the same structure as the one. The second ECU 2 executes a failure data storage routine and a failure data transmission routine similar to those of FIGS. 2 and 3, but in the failure data storage routine, the date and time data transmission request and the date and time data reception are performed in steps S2 and S3 of FIG. The terms "count value transmission request" and "count value reception" are to be read as "respectively". Also, the fault diagnosis tester 5
Performs a fault indication routine similar to that shown in FIG.

In this failure display routine, the second ECU 2
The count value indicating the time of failure occurrence is displayed in the order of occurrence of failure together with the failure code indicating one or more failure points related to, and therefore the time of occurrence of each failure is numerically displayed based on the counter value to confirm the order of occurrence of failure. It will be possible. Preferably, in the analysis of the failure data of the failure display routine (corresponding to step S22 in FIG. 4), the process of converting the count value into date / time data is performed. In this case, the date and time of failure occurrence is displayed instead of the numerical value display based on the count value, which is convenient for grasping the relevance of the failed part and thus for inspection and repair.
Note that, in connection with the conversion processing, for example, the date and time data when the counter of the first ECU 1 is activated (count value = 0) is changed to the second E
It may be stored in the memory of the CU 2 and the date and time data at the time of starting the counter may be provided from the second ECU 2 to the failure diagnosis tester 5 in the conversion process. Similar to the first embodiment, the failure diagnosis can be performed on the first ECU 1 and other ECUs by the same method.

Hereinafter, a fault diagnostic device according to a third embodiment of the present invention will be described with reference to FIG. The failure diagnosis apparatus of the present embodiment is composed of a plurality of electronic control units (ECU) 10 and a failure diagnosis tester 5, each ECU 10 has the same configuration, and replaces the timepiece 14 in comparison with the first ECU 1 shown in FIG. It is different in that a counter 20 is provided, and is otherwise the same as the first ECU 1 in FIG. 1. The sensor 17, the actuator 18, and the lamp 19 are connected to each EC.
It can be connected to U10, but element 1
It is not necessary to connect 7 to 19.

Each ECU 10 is a first EC of the second embodiment.
Similar to U1, it has a counter 20 and executes a failure data storage routine and a failure data transmission routine similar to those of FIGS. 2 and 3, as in the case of the second embodiment, but each ECU 10 has a counter. Therefore, the failure data storage routine does not include the count value sending request step and the count value receiving step corresponding to steps S2 and S3 of FIG.

Further, in the failure diagnosis apparatus of this embodiment, the counter 20 of each ECU 10 is activated when a failure related to each ECU 10 first occurs. That is, each ECU 10 periodically executes the counter starting routine illustrated in FIG. 6 while the ignition key is in the ON state. In this counter start-up routine, whether or not the counter 20 has been started is determined based on the count value of the counter 20 (step S
31) If the counter has not been activated, it is determined whether or not the first failure has occurred (step S32), the counter 20 is activated when the first failure has been determined (step S33), and then the counter is activated. The count value of 20 is incremented in a predetermined cycle.

As described above, in this embodiment, each ECU 10
The counter 20 is deactivated until the first failure related to (1) occurs, and the load on each ECU 10 is reduced by the amount that the operation control of the counter 20 is unnecessary. Note that each time the occurrence of a failure is detected in each ECU 10, the count value at the time of the failure occurrence is stored together with the failure code. Then, as in the case of the second embodiment, at the time of failure display by the failure diagnosis tester 5, the occurrence time of each failure is displayed numerically based on the count value, whereby the order of failure occurrence can be grasped.

Also in this embodiment, as in the case of the second embodiment, in the failure display routine executed by the failure diagnostic tester 5, the count value obtained by each ECU 10 is converted into date / time data to generate the date / time of occurrence of each failure. Fault diagnosis tester 5
Is preferably displayed on the display screen. Hereinafter, the failure diagnosis device according to the fourth embodiment of the present invention will be described.

The failure diagnosing apparatus of this embodiment is different from that of the third embodiment in the counter starting method, but is the same in other points. That is, in the present embodiment, each counter 20 of the plurality of ECUs 10 is activated in response to the activation command from the failure diagnosis tester 5. Therefore, for example, one or more counter starting tools, for example, the failure diagnosis tester 5 are connected to all the ECUs 10 via a branch circuit (not shown) when the vehicle is shipped. Then, when the ignition key of the vehicle is turned on,
Each ECU 10 starts a counter starting routine illustrated in FIG. 7.

In this counter starting routine, EC
The U10 determines whether or not the counter activation command is received from the failure diagnosis tester 5 (step S41), and if the activation command is not received, the counter activation routine in the current cycle is ended. On the other hand, when the counter activation command is received, the counter 20 is activated (step S42). Each time the ECU 10 detects the occurrence of a failure during vehicle operation, the count value of the counter 20 at that time is stored together with the failure code. Further, as in the case of the second and third embodiments, when a failure is displayed by the failure diagnostic tester 5, the time of occurrence of each failure is displayed numerically based on the count value, and preferably, the count value obtained by each ECU 10 is date and time. The date and time of occurrence of each failure is displayed together with the failure code through the conversion process for converting to data. Then, based on such a failure display, the failure point can be identified and repaired quickly and accurately, but the memory of the failure code is deleted after the failure point is repaired, while the increment of the count value continues before and after the repair. It is supposed to be done. Therefore, based on the failure display, it is possible to easily grasp the failure occurrence history after the vehicle is shipped, for example, the failure occurrence frequency at each location, the failure occurrence time interval, and the like.

The description of the failure diagnosis apparatus according to the embodiment of the present invention is completed above, but the present invention is not limited to the above-mentioned first to fourth embodiments, and can be variously modified. For example, in each of the embodiments, the failure diagnosis by the failure diagnosis tester is performed individually for each ECU.
In the fourth embodiment, the date / time data or the count value indicating the time of failure occurrence is common to all ECUs when viewed on the time axis. It is possible to display all the faults at once. In this case, some E
It is possible to more accurately and quickly grasp the relationship between a plurality of failures that have occurred in association with the CU, and thus the cause of the failure. Preferably, the failure display for a plurality of ECUs is performed in order of failure occurrence date and time, so that the relevance of the failure across the plurality of ECUs can be easily grasped.

Further, in the embodiment, the failure data storage in the ECU is stored in the memory in the order of the failure occurrence, and the failure display is displayed in the order of the data storage. However, it is not essential to store the failure data in the order of the failure occurrence. When displaying a failure by the diagnostic tester, the individual failure points may be rearranged in the order of failure occurrence or serial numbers indicating the order of failure occurrence may be added according to the date and time data and the count value included in the failure data.

Further, since the ECU equipped with the timekeeping means like the first ECU of the first embodiment is directly connected to the battery, no special ignition on / off countermeasure is required, but such an E
For the CU, as a battery replacement measure, a backup battery may be built in the ECU, or the date and time may be input again by a failure diagnosis tester or the like when the battery is replaced.

[0043]

According to the vehicle failure diagnosing device of the first aspect of the present invention, the electronic control unit capable of storing the failure data and the failure state are displayed so that the order of the failure occurrence can be known based on the failure data stored in the electronic control unit. Since it is equipped with a possible failure diagnosis means, it is possible to easily confirm the order of failure occurrence based on the failure status display, so that it is possible to know the location of the first failure occurrence and the order of subsequent failures, and thus the relationship between the failure locations. The cause of the occurrence can be easily identified, and the burden and cost required for the inspection and repair of the defective portion can be reduced accordingly.

In the failure diagnosis device of the second aspect, the electronic control device stores the failure data in the order of occurrence, and the failure diagnosis means displays the failure state in the order of the failure data stored in the electronic control device. Only by storing the failure data in the order of occurrence and displaying the failure status by the failure diagnosing means in the order of storage, the failure status can be displayed so that the failure occurrence order can be understood. In addition, no special procedure is required for such failure data storage and failure status display, and failure status display in which the order of failure occurrence can be easily realized can be realized.

The failure diagnosis device according to claim 3 includes the first and second fault diagnosis devices.
A plurality of electronic control units, which are electronic control units, are connected to each other by communication network means so that information can be transmitted to each other, the first electronic control unit has a clocking unit, and the second electronic control unit detects a failure occurrence. , The time value measured by the time measuring means is acquired and stored via the communication network means,
Since the failure status displayed by the failure diagnosis means includes the time value,
In the failure status display, the failure occurrence time points at individual failure points are respectively displayed to clarify the failure occurrence order. Further, the first electronic control unit provided with the time measuring means may be one, and one time measuring means is provided in plural. The cost of the failure diagnosis device can be reduced by sharing it with the electronic control device.

In the failure diagnosing device according to the fourth aspect of the invention, since the timekeeping means is composed of the clock means capable of determining the date and time, the date and time of failure occurrence can be included in the failure status display, and the cause of failure occurrence can be easily specified. In the failure diagnosing device of the fifth aspect, the counter means constitutes the time counting means, so that in the failure status display, each failure occurrence time point can be numerically displayed using the counter value to easily confirm the failure occurrence order.

In the failure diagnosing device according to the sixth aspect of the present invention, the counter means provided in each of the plurality of electronic control devices is activated when a failure relating to each electronic control device first occurs. While the control does not occur, the load on each electronic control unit can be reduced by the amount that the operation control of the counter means is unnecessary. In the failure diagnosis device according to claim 7, the failure diagnosis means includes clock means for specifying the failure occurrence date and time based on the count value of the counter means of each electronic control unit, so that the failure diagnosis means includes failure data including the count value. The date and time of failure occurrence can be acquired from the device, and the date and time of failure occurrence can be included in the failure status display. Further, since the counter means is used instead of the clock means, the device configuration is simplified.

In the failure diagnosing device according to the present invention, the counter means of each of the plurality of electronic control devices is activated in response to a command from the failure diagnosing device. Therefore, for example, a plurality of electronic control devices are shipped at the time of shipping. By simultaneously activating the counter means of the electronic control unit, the history of failure occurrence after shipment of the vehicle, for example, the number of failure occurrences at each location,
It is possible to easily grasp the time interval between failures.

[Brief description of drawings]

FIG. 1 is a schematic diagram of a vehicle failure diagnosis device according to a first embodiment of the present invention.

2 is a flowchart showing an example of a failure data storage routine executed by a second ECU shown in FIG.

FIG. 3 is a flowchart illustrating a failure data transmission routine executed by each ECU shown in FIG.

FIG. 4 is a flowchart illustrating a failure display routine executed by the failure diagnosis tester shown in FIG.

FIG. 5 is a schematic diagram of a failure diagnosis device according to a third embodiment of the present invention.

FIG. 6 is a flowchart illustrating a counter starting routine executed by each ECU shown in FIG.

FIG. 7 shows each E of the failure diagnosis device according to the fourth embodiment of the present invention.
It is a flow chart which illustrates a counter starting routine performed by CU.

[Explanation of symbols]

1 First ECU (first electronic control unit) 2 Second ECU (second electronic control unit) 3 communication lines (communication network means) 5 Failure diagnosis tester (failure diagnosis means) 10 ECU (electronic control unit) 11, 16 Interface circuit 12 Communication processing unit 13 CPU 14 clock 15 memory 19 alarm lamp 20 counter

─────────────────────────────────────────────────── ─── Continuation of front page (51) Int.Cl. ⁷ Identification code FI theme code (reference) G05B 23/02 301 G01M 17/00 J (72) Inventor Toshiaki Tateno 5-33, Shiba 5-chome, Minato-ku, Tokyo Issue Mitsubishi Motors Corporation F-term (reference) 3G084 DA27 EA07 EB06 EB22 3G093 BA24 BA26 DB00 DB23 5H223 AA10 CC08 DD03 EE06

Claims (8)

[Claims] 1. An electronic control device capable of storing failure data, and a failure diagnostic means capable of displaying a failure state so that a failure occurrence sequence can be known based on the failure data stored in the electronic control device. A vehicle failure diagnosis device characterized by the above. 2. The electronic control device stores the failure data in the order of occurrence, and the failure diagnosis means displays the failure state in the order of storage of the failure data in the electronic control device. The vehicle failure diagnosis device according to 1. 3. The electronic control device comprises a plurality of electronic control devices configured by first and second electronic control devices, and a communication network means for connecting the plurality of electronic control devices to each other so that information can be transmitted. The first electronic control unit has a timekeeping unit, and the second electronic control unit stores the timekeeping value clocked by the timekeeping unit via the communication network unit when a failure occurrence is detected. The vehicle failure diagnosis device according to claim 1, wherein the failure state displayed by the failure diagnosis means includes the time count value. 4. The vehicle failure diagnosis device according to claim 3, wherein the timekeeping means is a clock means capable of determining the date and time. 5. The vehicle failure diagnosis device according to claim 3, wherein the time counting means is a counter means for incrementing a count value in a predetermined cycle. 6. The electronic control device comprises a plurality of electronic control devices each having counter means for incrementing a count value in a predetermined cycle, and each of the plurality of electronic control devices has a failure related to the electronic control device. The vehicle failure diagnosis device according to claim 1, wherein the counter means is activated when the first occurs. 7. The vehicle according to claim 6, wherein the failure diagnosis means includes clock means for specifying a failure occurrence date and time based on the count value of the counter means of each of the electronic control units. Fault diagnosis device. 8. The electronic control device comprises a plurality of electronic control devices each having counter means for incrementing a count value in a predetermined cycle, and each of the counter means of the plurality of electronic control devices has the failure diagnosis means. The failure diagnosis device for a vehicle according to claim 1, which is activated in response to a command from the vehicle.