JP2020148531A - Vehicle electronic controller, request device, and fault detection system - Google Patents

Abstract

To provide technology with which it is possible to prevent vehicle inspection from being mistakenly passed.SOLUTION: A fault detection system 1 comprises: a vehicle electronic controller 10 having a fault storage device 14 mounted in a vehicle and in which a fault code is stored; and a request device 3 for outputting a readout request for reading out the fault code. In the vehicle electronic controller, an additional information storage unit 56 stores additional information, in association with the fault code, that indicates whether or not the stored content of the fault code in the fault storage device is correct. The fault detection system includes recognition units 57, 76. The recognition units acquire the additional information correlated to the fault code which is requested to be read out, determines on the basis of the additional information whether or not the stored content of the fault code is appropriate, and when not determined as appropriate, causes the fact that the stored content of the fault code is not appropriate to be recognized by the request device. The fault code is a specific fault code used for determination in vehicle inspection.SELECTED DRAWING: Figure 1

Description

The present disclosure relates to a technique for detecting the occurrence of an abnormality in a vehicle.

There is known a technique in which an in-vehicle electronic control unit (hereinafter, ECU) detects that some abnormality has occurred in various in-vehicle sensors, actuators, or the like by OBD, and stores a failure code representing the detected result.

For example, in Patent Document 1, a failure code stored in an ECU mounted on a vehicle is read out by an inspection tool which is an external device of the vehicle and displayed, and a maintenance worker confirms the failure code displayed on the inspection tool. The technology for recognizing the faulty part is described.

Japanese Unexamined Patent Publication No. 2005-81849

ECU is an abbreviation for Electronic Control unit. OBD is an abbreviation for On board Diagnostics, which means to perform so-called self-diagnosis, that is, abnormal diagnosis.
In the abnormality diagnosis, the presence or absence of an abnormality is detected for a predetermined diagnosis item for the vehicle, and the failure code corresponding to the detected abnormality is recorded. Various failure codes are preset according to the diagnostic items.

In recent years, at least one of the failure codes has been used, which indicates that an abnormality that does not meet the vehicle safety standards has occurred in the automobile inspection registration system (hereinafter, vehicle inspection) (hereinafter, specific failure code). An automobile inspection method has been proposed. For example, when the inspection tool reads out the specific failure code recorded by the ECU mounted on the vehicle, it is determined that the vehicle inspection has failed.

In such an automobile inspection method, when passing the automobile inspection, it is necessary to initialize, that is, erase the specific failure code stored in the ECU. The specific failure code stored in the ECU can be erased by using an inspection tool.

However, if the specific failure code recorded in the ECU is erroneously erased, it is considered that the inspection tool performs the vehicle inspection based on the erroneously erased specific failure code. That is, if a vehicle inspection is performed by an inspection tool using such an improper specific failure code, there is a risk of passing the vehicle inspection by mistake as if the failure has not been detected.

Further, in such an automobile inspection method, if an erroneous specific failure code is recorded, there is a possibility that the vehicle inspection may be erroneously passed based on the erroneous specific failure code.
Further, in such an automobile inspection method, for example, instead of the ECU mounted on the vehicle that has not been inspected and the vehicle that has not been inspected, the specific failure code is not detected and the vehicle has already passed the inspection. If the ECU of a vehicle is improperly mounted, a vehicle that has not been inspected may mistakenly pass the inspection.

One aspect of the present disclosure is to provide a technique that can prevent accidentally passing a vehicle inspection.

One aspect of the present disclosure is a vehicle electronic control device (10) having a failure storage device (14) mounted on the vehicle and storing a failure code indicating an abnormality of the vehicle, and reading out the failure code from the vehicle electronic control device. A failure detection system (1) including a request device (3) for outputting a request. The vehicle electronic control unit includes a code storage unit (55) and an additional information storage unit (56). The code storage unit acquires the diagnosis result from the diagnosis execution unit (54) that executes the abnormality diagnosis of the vehicle, and stores the failure code in the failure storage device based on the diagnosis result.

The additional information storage unit acquires additional information for indicating whether or not the storage content of the failure code in the failure storage device is appropriate, and stores the additional information in association with the failure code. The failure detection system includes recognition units (57, 76). The recognition unit acquires additional information associated with the failure code that is the target of the read request, determines whether or not the stored content of the failure code is appropriate based on the additional information, and determines that it is not appropriate. In this case, the requesting device is made to recognize that the stored content of the failure code is not appropriate.

The failure code is a specific failure code used for determining the inspection of the vehicle.
As a result, the requesting device can recognize that the stored content of the specific failure code targeted for the read request is not appropriate based on the additional information. Then, for example, when it is recognized that the stored content of the specific failure code is not appropriate, it is possible to prevent the vehicle from passing the vehicle inspection by mistake.

A block diagram showing the configuration of a failure detection system, a vehicle control device, and an inspection tool. The functional block diagram explaining the function of the ECU. A functional block diagram illustrating the functions of the tool control unit. Flowchart of initialization process. Flowchart of additional information storage processing. Flowchart of processing during ECU drive. Flowchart of processing while the engine is running. Flowchart of vehicle side recognition processing. Flowchart of request side recognition processing.

Hereinafter, embodiments of the present disclosure will be described with reference to the drawings.
[1. First Embodiment]
[1-1. overall structure]
The failure detection system 1 shown in FIG. 1 is a system for detecting that an abnormality has occurred in a vehicle. The failure detection system 1 includes a vehicle control device 2 mounted on the vehicle and an inspection tool 3 used by maintenance personnel at a maintenance shop or the like. The vehicle control device 2 includes at least one ECU 10.

In the failure detection system 1, the vehicle control device 2 is configured to store a failure code (hereinafter, DTC). The DTC is a failure code indicating an abnormality in the vehicle on which the vehicle control device 2 is mounted. DTC is an abbreviation for Diagnostic Trouble Code. Among the DTCs, the DTC showing an abnormality that does not meet the safety standards of the Road Transport Vehicle Law is called a specific DTC.

In the vehicle control device 2, when an abnormality that does not satisfy the safety standard of the Road Transport Vehicle Law is detected in the vehicle, the ECU 10 stores the specific DTC corresponding to the abnormality in the storage device included in the ECU 10.

In the failure detection system 1, the specific DTC is used for determining the vehicle inspection. At the time of vehicle inspection using the specific DTC, the inspection tool 3 and the ECU 10 are connected by a cable 40 so as to communicate with each other at a maintenance shop or the like. The inspection tool 3 outputs a read request for reading the specific DTC to the ECU 10. When the specific DTC is read from the ECU 10 by the inspection tool 3, the vehicle inspection is determined to be unacceptable.

That is, the vehicle in which the specific DTC is stored in the ECU 10 fails the vehicle inspection.
Information about the specific DTC (hereinafter, specific DTC information) such as information on which DTC to use as the specific DTC and information indicating the version of the DTC is stored in the server 4 of the management mechanism that manages the vehicle inspection. ing. The management mechanism refers to a mechanism that manages vehicle inspections by a specific DTC.

In the present embodiment, the inspection tool 3 acquires and updates the specific DTC information from the server 4, and then executes the vehicle inspection using the specific DTC as described above. That is, the inspection tool 3 determines whether or not the vehicle inspection has passed. In this case, the inspection tool 3 acquires the specific DTC information from the server 4 and saves the acquired specific DTC information in the inspection tool 3. Then, the inspection tool 3 determines whether or not the vehicle inspection has passed or failed based on the stored specific DTC information.

[1-2. Each configuration]
Next, each configuration of the failure detection system 1 of the present embodiment will be described in detail.
(1) Vehicle Control Device The vehicle control device 2 includes at least one ECU 10. Further, the vehicle control device 2 includes a battery 15. The ECU 10 executes predetermined vehicle control for the ECU 10.

The ECU 10 includes a microcomputer (hereinafter, microcomputer) 11, a communication interface (hereinafter, communication I / F) 12, an EEPROM 13, and a static RAM (hereinafter, SRAM) 14. The microcomputer 11 includes a CPU 21 and a semiconductor memory (hereinafter, memory) 22 such as a ROM, RAM, and flash memory. Electric power is constantly supplied to the ECU 10 by the battery 15.

The communication interface 12 communicates with the inspection tool 3 via the cable 40.
The EEPROM 13 is a rewritable non-volatile memory. The EEPROM 13 may be a flash memory or the like. The EEPROM 13 stores the unique identification information in advance. The unique identification information is identification information that can identify the vehicle and is information unique to the vehicle. Specifically, the VIN code is stored as the unique identification information.

Further, although not shown, the ROM or the EEPROM 13 stores at least a list of diagnostic items that can be executed by the ECU 10 and a list of DTCs associated with the diagnostic items in advance. Further, although not shown, a list indicating which of the DTCs is the specific DTC is stored in the ROM or the EEPROM 13 in advance.

The SRAM 14 is a volatile memory that operates by constantly receiving power supplied from the battery 15 regardless of whether the ignition switch is on or off. That is, the SRAM 14 always stores and holds the written data while the power supply from the battery 15 continues.

The SRAM 14 has a specific DTC storage area 141 and an additional information storage area 142. The specific DTC storage area 141 is an area in which the specific DTC is stored. The additional information storage area 142 is an area in which additional information described later is stored. The area in which the specific DTC is stored and the area in which additional information about the specific DTC is stored are associated with each other. For example, when a specific DTC is stored in the specific DTC storage area 141, additional information is stored in the area of the additional information storage area 142 associated with the specific DTC storage area 141 in which the specific DTC is stored. To.

Various functions of the ECU 10 are realized by the CPU 51 executing a program stored in the memory 22. Moreover, when this program is executed, the method corresponding to the program is executed. The ECU 10 may be provided with one microcomputer or may be provided with a plurality of microcomputers.

As shown in FIG. 2, the ECU 10 includes an initialization unit 51, an elapsed time generation unit 52, a monitoring unit 53, a diagnosis execution unit 54, and a code storage as a configuration of functions realized by the CPU 51 executing a program. A unit 55, an additional information storage unit 56, a vehicle-side recognition unit 57, and an information output unit 58 are provided.

The method for realizing these elements constituting the ECU 10 is not limited to software, and one or more hardware may be used for one or all of the elements. For example, when the above function is realized by an electronic circuit which is hardware, the electronic circuit may be realized by a digital circuit including a large number of logic circuits, an analog circuit, or a combination thereof.

Upon receiving the initialization request, the initialization unit 51 executes an initialization process described later to initialize at least the storage contents of the specific DTC storage area 141 and the storage contents of the additional information storage area 142 in the SRAM 14. That is, reset. Along with this, the specific DTC stored in the specific DTC storage area 141, the elapsed time after initialization and the travel history stored in the additional information storage area 142 are initialized.

The initialization request can be transmitted to the ECU 10 from, for example, another ECU mounted on the vehicle, the inspection tool 3, or the like.
The initialization unit 51 may be configured to initialize at least the stored contents of the SRAM 14 as the initialization process is executed, or may be configured to initialize the entire ECU 10. Further, the initialization unit 51 may be configured to execute the above-mentioned initialization other than when the initialization request is received. For example, the initialization unit 51 may be configured to perform the above-mentioned initialization even when the power supply to the ECU 10 by the battery 15 is cut off due to the removal of the ECU 10 from the vehicle or the like.

The elapsed time generation unit 52 generates elapsed time information and stores it in the SRAM 14. The elapsed time information is information representing the elapsed time since the ECU 10 was initialized. The elapsed time information may be the elapsed time after initialization. The elapsed time after initialization is the elapsed time itself after the ECU 10 is initialized. Further, the elapsed time information does not have to be the elapsed time after initialization as long as it is a parameter that increases with the passage of time after the ECU 10 is initialized.

For example, the elapsed time information may be a travel history that represents the history of the vehicle traveling since the ECU 10 was initialized. Specific examples of the travel history include the number of times the ignition switch is turned on and off (hereinafter, the number of times the ignition switch is turned on and off) after the ECU 10 is initialized.

In the present embodiment, the elapsed time generation unit 52 is configured to generate the number of on / off times as a running history and the above-mentioned elapsed time after initialization as elapsed time information and store them in the SRAM 14. The number of on / off may be counted, for example, as one turn after the ignition switch is turned on.

The monitoring unit 53 repeatedly monitors the state of the ECU 10 at a predetermined cycle, and repeatedly generates state information. The state information is information indicating whether or not an abnormality has occurred in the ECU 10.

In this embodiment, memory abnormality information is used as state information. The memory abnormality information is information indicating whether or not a ROM abnormality or a RAM abnormality in the memory 22 is detected. This is because if an abnormality in the ROM or an abnormality in the RAM is detected, it is considered that the abnormality has occurred in the ECU 10.

For example, the ROM abnormality referred to here may be an abnormality in the write value of the ROM or an abnormality in reading. The RAM abnormality may be an abnormality when writing to the RAM or an abnormality when reading. These abnormalities can be detected by, for example, the CRC or checksum of the data to be written or read.

The monitoring unit 53 is configured to detect a ROM abnormality or a RAM abnormality in the memory 22, and when these abnormalities are detected, generate memory abnormality information indicating that an abnormality has occurred in the ECU 10.

The diagnosis execution unit 54 executes an abnormality diagnosis in order to detect an abnormality in the vehicle. The diagnosis execution unit 54 may be configured to store the readiness flag in the SRAM 14 when the abnormality diagnosis is completed. Completion of the abnormality diagnosis here means that normality or abnormality is determined by the abnormality diagnosis. Diagnosis results are indicated as either normal or abnormal. The diagnosis execution unit 54 diagnoses whether or not any abnormality has occurred in various sensors, actuators, etc. mounted on the vehicle by executing the abnormality diagnosis for each predetermined specific diagnosis item.

The specific diagnostic item is a diagnostic item necessary for determining the pass / fail of the vehicle inspection. Specific diagnostic items include, for example, diagnosing the actuator state such as the operating characteristics of the actuator and the terminal state (that is, OPEN or SHORT). Specifically, for the specific diagnostic item, the detected values of various sensors, the current consumption of the actuator, and the like are monitored, and the normality or abnormality of the specific diagnostic item is determined based on the monitor result.

However, the specific diagnostic items are not limited to these, and a wide variety of items may be included. In addition, a wide variety of means may be included as specific means for determining the normality and abnormality of a specific diagnostic item.

When the result that an abnormality has occurred in the specific diagnostic item is obtained, the code storage unit 55 stores the specific DTC corresponding to the specific diagnostic item in the specific DTC storage area 141.

In the present embodiment, the diagnosis execution unit 54 stores the diagnosis result in the SRAM 14 by using at least one of the abnormality flag and the normal flag. The abnormality flag is a flag that is set when the result of the abnormality diagnosis is abnormal and reset when the result is normal. The normal flag is a flag that is reset when the result of the abnormality diagnosis is abnormal and is set when the result is normal.

Specifically, the diagnosis execution unit 54 executes an abnormality diagnosis as follows, for example. Here, an example in which the diagnosis execution unit 54 monitors the current consumption of the actuator for a specific diagnosis item will be described. First, the diagnosis execution unit 54 repeatedly acquires the current value of the actuator or the like at predetermined time intervals. The diagnosis execution unit 54 determines whether or not the current value of the actuator or the like has been acquired a predetermined number of times (hereinafter, the number of acquisitions). For example, when it is determined that the average value of the current values has been acquired, the diagnosis execution unit 54 determines whether or not the average value of the current values is equal to or greater than a predetermined determination threshold value.

The diagnosis execution unit 54 sets an abnormal flag and resets the normal flag when it determines that the current value is equal to or higher than the determination threshold value, and resets the abnormal flag and resets the normal flag when it determines that the current value is less than the determination threshold value. To set. The diagnosis execution unit 54 stores these flags in the SRAM 14.

In this way, the abnormality diagnosis is performed, and the diagnosis result is stored as a normal flag and an abnormality flag. That is, it takes time from the start to the completion of the abnormality diagnosis, in other words, until the diagnosis result is stored in the SRAM 14. The term required for diagnosis as described below means the time required for the abnormality diagnosis by the diagnosis execution unit 54, that is, the time required from the start to the completion of the abnormality diagnosis.

The procedure for diagnosing an abnormality is not limited to this. The diagnosis execution unit 54 may be configured to execute an abnormality diagnosis for various specific diagnosis items by various procedures and store the diagnosis result. Further, the diagnosis execution unit 54 may be configured to execute an abnormality diagnosis for a plurality of specific diagnosis items and store the diagnosis result in the SRAM 14 for each specific diagnosis item.

The code storage unit 55 is activated when the abnormality diagnosis by the diagnosis execution unit 54 is completed. When the abnormality diagnosis is completed, the code storage unit 55 acquires the diagnosis result by the diagnosis execution unit 54, and stores the specific DTC corresponding to the generated abnormality in the specific DTC storage area 141 based on the diagnosis result. When storing the specific DTC, the code storage unit 55 stores the specific DTC in association with the specific diagnostic item of the specific DTC and the diagnosis result of the specific diagnostic item. The diagnosis result referred to here is the above-mentioned abnormality flag and normal flag.

For example, when the diagnosis execution unit 54 determines that an abnormality has occurred, the code storage unit 55 writes the specific DTC targeted by the code storage unit 55 into the specific DTC storage area 141. When it is determined that an abnormality has occurred, it means that the abnormality flag is set or the normal flag is reset.

The specific DTC targeted by the code storage unit 55, that is, the specific DTC targeted by whether or not the code storage unit 55 writes to the specific DTC storage area 141, is an abnormality diagnosis executed by the diagnosis execution unit 54. Refers to a specific DTC corresponding to a specific diagnostic item. When the code storage unit 55 determines that no abnormality has occurred as a result of the abnormality diagnosis by the diagnosis execution unit 54, the code storage unit 55 does not write the specific DTC targeted by the code storage unit 55 into the specific DTC storage area 141.

After the diagnosis result is stored in the SRAM 14 by the diagnosis execution unit 54, the additional information storage unit 56 acquires the additional information generated by the additional information generation unit, associates the additional information with the specific DTC, and stores the additional information in the SRAM 14. Store in area 142. The additional information storage unit 56 realizes these functions by executing the additional information storage process described later.

The additional information is information for indicating whether or not the stored content of the specific DTC in the specific DTC storage area 141 (hereinafter, the stored content of the specific DTC) is appropriate.
The storage content of the specific DTC referred to here means the storage content of the storage area for each specific DTC in the specific DTC storage area 141. The specific DTC storage area 141 may be in either a state in which the specific DTC is stored or a state in which the specific DTC is not stored and is still initialized. When the specific DTC is stored in the specific DTC storage area 141, the specific DTC itself corresponds to the storage content of the specific DTC. When the specific DTC is not stored in the specific DTC storage area 141, the fact that the specific DTC is not stored, in other words, that the abnormality corresponding to the specific DTC has not occurred corresponds to the stored contents of the specific DTC. ..

In addition, "appropriate" here means that it is valid, in other words, that it can be trusted. For example, in the following cases (a)-(c), the stored contents of the specific DTC are considered to be appropriate.

(A) <When an abnormality diagnosis is executed by the diagnosis execution unit 54, the diagnosis result is stored, and the stored content of the specific DTC is determined based on the diagnosis result>
That is, when the diagnosis result by the diagnosis execution unit 54 is not stored, the stored content of the specific DTC may not be appropriate.

For example, whether or not the abnormality diagnosis is executed and the specific DTC is stored can be determined based on the information indicating that the diagnosis result is stored in SRAM 14. This is because if the diagnosis result is stored in the SRAM 14, it is considered that the stored content of the specific DTC is determined based on the diagnosis result.

Further, for example, whether or not the abnormality diagnosis is executed and the specific DTC is stored can be determined based on the elapsed time information. When the elapsed time information represents a time longer than the above-mentioned required diagnosis time, the information in the specific DTC storage area 141 is considered to be appropriate. If the elapsed time after the initialization of the ECU 10 is longer than the required time for diagnosis, it is considered that the abnormality diagnosis is executed by the diagnosis execution unit 54 after the initialization of the ECU 10 and the specific DTC is stored on it. is there.

The diagnosis execution information referred to below refers to information indicating whether or not the specific DTC as a diagnosis result is stored in the specific DTC storage area 141 after the abnormality diagnosis is executed by the diagnosis execution unit 54. The diagnosis execution information may include the above-mentioned elapsed time information and the diagnosis result by the diagnosis execution unit 54 as described later. The elapsed time information may include the elapsed time after initialization and the traveling history.

(B) <When the state of ECU 10 is normal>
That is, if the state of the ECU 10 is not normal, the stored contents of the specific DTC generated by the ECU 10 may not be appropriate. Whether or not the state of the ECU 10 is normal can be determined based on the above-mentioned state information.

(C) <When the vehicle is properly equipped with a one-to-one ECU 10>
For example, the following cases can be considered as the case where the ECU 10 having a one-to-one correspondence is not correctly mounted on the vehicle. That is, when the vehicle on which the ECU 10 is mounted (hereinafter, also referred to as the own vehicle) has not been inspected and the ECU of another vehicle for which the vehicle inspection has been normally completed is improperly mounted as the ECU 10 of the own vehicle. Is.

In such a case, the stored content of the specific DTC generated by the ECU of another vehicle for which the vehicle inspection has been normally completed is not appropriate for the own vehicle. Whether or not the one-to-one correspondence ECU 10 is correctly mounted on the vehicle can be determined by transmitting an encrypted signal from the ECU 10 to the inspection tool 3 using, for example, unique identification information such as a VIN code. That is, it is possible to determine whether or not the encrypted signal can be decrypted by the inspection tool 3.

In the present embodiment, as the additional information, the elapsed time after initialization as the above-mentioned elapsed time information and the memory abnormality information as the state information are used.
In the above cases (a)-(c), the stored contents of the specific DTC are considered to be appropriate.

For example, in the present embodiment, when the specific DTC is stored in the specific DTC storage area 141 by the code storage unit 55, the additional information storage unit 56 acquires the elapsed time after initialization and the memory abnormality information as additional information. To do.

Then, the additional information storage unit 56 stores the additional information in a predetermined area of the additional information storage area 142, which is the area associated with the above-mentioned specific DTC storage area in the specific DTC storage area 141. The specific DTC described above refers to a specific DTC stored by the code storage unit 55. In the present embodiment, the elapsed time generation unit 52 and the monitoring unit 53 correspond to the above-mentioned additional information generation unit.

The recognition unit is provided in at least one of the ECU 10 and the inspection tool 3. In this embodiment, the recognition unit is provided in both the ECU 10 and the inspection tool 3. In the following, the recognition unit included in the ECU 10 is referred to as a vehicle side knowledge unit 57, and the recognition unit included in the inspection tool 3 is referred to as a request side recognition unit 76.

When the read request for reading the specific DTC is output from the inspection tool 3, the vehicle-side recognition unit 57 acquires additional information of the specific DTC that is the target of the read request. Then, the vehicle side recognition unit 57 determines whether or not the stored content of the specific DTC is appropriate based on the additional information, and if it is determined that the stored content of the specific DTC is not appropriate, the stored content of the specific DTC is not appropriate for the inspection tool 3. Make them aware of that. The vehicle side recognition unit 57 executes the vehicle side recognition process described later in order to realize the above-mentioned function.

When the vehicle side recognition unit 57 determines that the stored content of the specific DTC is not appropriate, the vehicle side recognition unit 57 gives a no response or a negative response to the inspection tool 3, so that the stored content of the specific DTC is not appropriate for the inspection tool 3. To recognize. In the present embodiment, the vehicle-side recognition unit 57 makes the inspection tool 3 recognize that the stored content of the specific DTC is not appropriate by performing no response to the inspection tool 3. No response means that no response is given to the inspection tool 3. The negative response is a response that rejects the read request.

The information output unit 58 outputs the stored contents of the specific DTC and the additional information associated with the specific DTC to the inspection tool 3 when the predetermined output conditions are satisfied. In the present embodiment, the information output unit 58 uses that the read request is output as an output condition. Further, in the present embodiment, the information output unit 58 encrypts and sends the stored contents of the specific DTC and the additional information based on the VIN code which is the unique identification information.

It should be noted that S31 in the ECU driving process described later corresponds to the elapsed time generation unit 52 that generates the elapsed time after initialization, and S32 corresponds to the monitoring unit 53 that generates the memory abnormality information as the state information. Further, S41 in the engine driving process described later corresponds to the elapsed time generation unit 52 that generates the traveling history. Further, S110 and S180 of the vehicle side recognition process described later correspond to the vehicle side recognition unit 57, and S150 corresponds to the information output unit 58.

(2) Inspection Tool As shown in FIG. 1, the inspection tool 3 is a device used by an operator and is a device outside the ECU 10. The inspection tool 3 is connected to the communication line 16 in the vehicle via the cable 40 and is configured to be able to communicate with the ECU 10 with each other. The inspection tool 3 outputs a read request for reading the specific DTC to the ECU 10.

The inspection tool 3 includes a tool control unit 31. The inspection tool 3 may include an operation unit 32, a display 33, and a tool communication unit 34.
The operation unit 32 receives various instruction inputs from the worker. The display 33 displays various information. The tool communication unit 34 communicates with the above-mentioned server 4. The communication with the server 4 may be wireless communication or wired communication.

The tool control unit 31 includes a microcomputer 61. The microcomputer 61 includes a CPU 71 and a memory 72. In the memory 72, a list for associating the DTC corresponding to the ECU 10 included in the vehicle with the specific DTC among the DTCs is stored.

Various functions of the tool control unit 31 are realized by the CPU 71 executing a program stored in the memory 72. Moreover, when this program is executed, the method corresponding to the program is executed.

As shown in FIG. 3, the tool control unit 31 includes a request unit 75 and a request side recognition unit 76 as a configuration of functions realized by the CPU 71 executing a program.
The request unit 75 outputs a read request for reading the specific DTC from the ECU 10 to the ECU 10 in accordance with the instruction of the worker from the operation unit 32.

After the read request is output by the request unit 75, the request side recognition unit 76 acquires the specific DTC to be the target of the read request and the additional information associated with the specific DTC from the ECU 10. Then, the requesting side recognition unit 76 determines whether or not the stored content of the specific DTC is appropriate based on the additional information, and if it is determined that the stored content of the specific DTC is not appropriate, the stored content of the specific DTC is not appropriate for the inspection tool 3. Make them aware of that.

The request side recognition processes S230, S250, S260, and S280, which will be described later, correspond to the request side recognition unit 76.
[1-2. processing]
(1) Process executed by the ECU (1-1) Initialization process The initialization process executed by the initialization unit 51 of the ECU 10 will be described with reference to the flowchart of FIG. The initialization process is a process that is started when an initialization request is received.

In the present embodiment, the initialization process is also activated when the power supply to the ECU 10 by the battery 15 is cut off due to the removal of the ECU 10 from the vehicle or the like.
Further, in the present embodiment, the initialization process is started when a clear command is received from any one of the ECU 10, the other ECU, and the inspection tool 3. The clear command is an instruction for resetting the stored contents of the specific DTC in the specific DTC storage area 141 and the elapsed time information in the additional information storage area 142. In the present embodiment, the elapsed time information includes the elapsed time after initialization and the number of on / off times as a running history.

In S11, the ECU 10 erases the stored contents of the specific DTC storage area 141. As a result, the stored contents of the specific DTC are initialized. Further, the ECU 10 erases the diagnosis result by the diagnosis execution unit 54 stored in the additional information storage area 142. As a result, the history indicating that the diagnosis has been executed by the diagnosis execution unit 54 is deleted.

In S12 and S13, the ECU 10 resets the elapsed time information. In the present embodiment, the elapsed time information is information used as additional information. Specifically, in S12, the ECU 10 resets the elapsed time after initialization stored in the additional information storage area 142. That is, the elapsed time after initialization is set to 0, which is the initial value.

In S13, the ECU 10 resets the travel history stored in the additional information storage area 142. That is, the running history is set to 0, which is an initial value. In the present embodiment, the number of on / off times as the running history is set to 0, which is the initial value. The ECU 10 completes the initialization process.

(1-2) Additional Information Storage Process Next, the additional information storage process executed by the additional information storage unit 56 of the ECU 10 will be described with reference to the flowchart of FIG. The additional information storage process is started when the code storage unit 55 is started.

In S21, the ECU 10 acquires a time stamp which is information about the time. The ECU 10 is configured to have a function of generating a time stamp in advance. In the present embodiment, the ECU 10 stores the time stamp in the additional information storage area 142 in association with the specific DTC that triggered the activation of the additional information storage process. The specific DTC that triggered the activation of the additional information storage process corresponds to the specific DTC that is the target of whether or not the code storage unit 55 described above stores.

In S22, the ECU 10 acquires the elapsed time after initialization generated by the elapsed time generation unit 52. Then, the ECU 10 stores the elapsed time after initialization in the additional information storage area 142 in association with the specific DTC that triggered the activation of the additional information storage process.

In S23, the ECU 10 acquires the travel history generated by the elapsed time generation unit 52. In the present embodiment, the traveling history is on / off information. Then, the ECU 10 stores the travel history in the additional information storage area 142 in association with the specific DTC that triggered the activation of the additional information storage process. The ECU 10 completes the additional information storage process.

(1-3) ECU driving process Next, the ECU driving process executed by the ECU 10 will be described with reference to the flowchart of FIG. The ECU-driving process is a process that is repeatedly executed in a predetermined cycle (hereinafter, the first processing cycle) while the electric power is being supplied to the ECU 10 by the battery 15 and while the ECU 10 is starting up.

In S31, the ECU 10 updates the elapsed time after initialization. Specifically, the ECU 10 acquires the elapsed time after initialization and generates a value obtained by adding the first processing cycle to the elapsed time after initialization as a new elapsed time after initialization. Then, the ECU 10 overwrites the new elapsed time after initialization with the area in which the original elapsed time after initialization is stored in the SRAM 14.

The ECU 10 updates the state information in S32. In this embodiment, the above-mentioned memory abnormality information is used as the state information. The ECU 10 acquires the state information, uses the acquired state information as new state information, and overwrites the new state information in the area in which the original state information in the SRAM 14 is stored.

The ECU 10 has completed the process of driving the ECU. As a result, the elapsed time after initialization and the latest value of the state information are stored in the SRAM 14.
(1-4) Process during engine drive Next, the process during engine drive executed by the ECU 10 will be described with reference to the flowchart of FIG. 7. The process during engine drive is a process that is repeatedly executed at a predetermined cycle (hereinafter, a second process cycle) when the vehicle is running, that is, while the engine is being driven.

The ECU 10 updates the travel history in S41. In the present embodiment, the above-mentioned on / off number of times is used as the traveling history. The ECU 10 acquires the number of on / off times as a travel history, and adds the number of times the ignition switch is turned on and off during the second processing cycle to the number of times of on / off to calculate a new number of on / off times. The ECU 10 overwrites the new on / off number in the area where the original on / off number in the SRAM 14 is stored.

The ECU 10 ends the processing while the engine is being driven. As a result, the latest value of the number of on / off times as a running history is stored in the SRAM 14.
(1-5) Vehicle-side recognition process Next, the vehicle-side recognition process executed by the ECU 10 will be described with reference to the flowchart of FIG. The vehicle-side recognition process is activated when a read request is received from the inspection tool 3.

The ECU 10 determines in S110 whether or not an appropriate response to the read request is possible. In the present embodiment, the ECU 10 determines that an appropriate response to the read request is possible when the stored content of the specific DTC in the specific DTC storage area 141 is appropriate.

The ECU 10 determines whether or not the stored content of the specific DTC is appropriate based on the additional information. In the present embodiment, the ECU 10 acquires the elapsed time information as additional information, and when the elapsed time information represents a time longer than the time required for diagnosis, determines that the information in the specific DTC storage area 141 is appropriate.

The ECU 10 shifts the process to S120 when it determines that an appropriate response to the read request is possible, and shifts the process to S160 when it determines that an appropriate response to the read request is not possible.

In S120, the ECU 10 acquires the stored contents of the specific DTC corresponding to the read request from the specific DTC storage area 141.
In S130, the ECU 10 acquires the elapsed time information of the additional information associated with the specific DTC corresponding to the read request from the additional information storage area 142. In this embodiment, the elapsed time after initialization as the elapsed time information is acquired.

In S140, the ECU 10 acquires the state information of the additional information associated with the specific DTC corresponding to the read request from the additional information storage area 142. In this embodiment, memory abnormality information as state information is acquired.

In S150, the ECU 10 outputs to the inspection tool 3 the stored contents of the specific DTC corresponding to the read request and the additional information associated with the specific DTC corresponding to the read request. In the present embodiment, the ECU 10 encrypts and sends the stored contents of the specific DTC and the additional information based on the identification information unique to the vehicle. As the identification information, the VIN code stored in the VIN storage area 131 is used. The ECU 10 ends the vehicle side recognition process after finishing the output to the inspection tool 3.

When the ECU 10 determines that the stored content of the specific DTC is not appropriate, in S160, the inspection tool 3 is made to recognize that the stored content of the specific DTC is not appropriate by performing no response to the inspection tool 3. .. After making no response to the inspection tool 3, the ECU 10 ends the vehicle-side recognition process.

(2) Process executed by the inspection tool Next, the request side recognition process executed by the tool control unit 61 will be described with reference to the flowchart of FIG. The request side recognition process is started when the inspection tool 3 transmits a read request for the specific DTC to the ECU 10.

In S210, the tool control unit 61 determines whether or not there is a response to the read request from the ECU 10. The tool control unit 61 shifts the process to S220 when there is no response from the ECU 10, and shifts the process to S230 when there is a response from the ECU 10.

In S220, the tool control unit 61 determines whether or not the time during which there is no response from the ECU 10 (hereinafter, response waiting time) is less than a predetermined time (hereinafter, waiting time threshold value). The ECU 10 shifts the process to S210 when the response waiting time is less than the waiting time threshold value, and shifts the process to S280 when the response waiting time is equal to or more than the waiting time threshold value.

In S230, the tool control unit 61 acquires the response signal transmitted from the ECU 10. That is, the tool control unit 61 acquires the stored contents and additional information of the specific DTC. If these are encrypted when transmitted from the ECU 10, the ECU 10 decrypts them in this step.

In the subsequent S240, the tool control unit 61 determines in the ECU 10 whether or not an abnormality corresponding to the specific DTC that is the target of the read request has occurred based on the stored contents of the specific DTC. For example, when the specific DTC is stored as the storage content of the specific DTC that is the target of the read request, the ECU 10 determines that an abnormality corresponding to the specific DTC has occurred. In other words, when the specific DTC is not stored as the storage content of the specific DTC that is the target of the read request, it is determined that the abnormality corresponding to the specific DTC has not occurred.

The tool control unit 61 shifts the process to S280 when it is determined in the ECU 10 that an abnormality corresponding to the specific DTC that is the target of the read request has occurred, and processes when it is determined that the abnormality has not occurred. To S250.

In S250 and S260, the tool control unit 61 determines whether or not the stored content of the specific DTC transmitted from the ECU 10 is appropriate based on the additional information transmitted from the ECU 10.

In S250, the tool control unit 61 transmits from the ECU 10 when it is determined that the stored content of the specific DTC is based on the diagnosis result of the abnormality diagnosis by the diagnosis execution unit 54 based on the additional information transmitted from the ECU 10. It is determined that the stored content of the specified DTC is appropriate.

Specifically, in the present embodiment, the tool control unit 61 makes a determination based on the elapsed time information in the additional information. In the present embodiment, the tool control unit 61 determines that it is appropriate when the elapsed time after initialization is equal to or longer than the required time for diagnosis based on the elapsed time after initialization as the elapsed time information. When the tool control unit 61 determines that it is appropriate, it shifts the process to S260, and when it determines that it is not appropriate, it shifts the process to S280.

The diagnosis required time, which is a threshold value required for determination, may be stored in the memory 72 in advance, or may be transmitted from the ECU 10 together with additional information.
In S260, the tool control unit 61 determines that the stored content of the specific DTC transmitted from the ECU 10 is appropriate when the ECU 10 is determined to be normal based on the additional information transmitted from the ECU 10.

Specifically, in the present embodiment, the tool control unit 61 makes a determination based on the state information of the additional information. When the tool control unit 61 determines that it is appropriate, it shifts the process to S270, and when it determines that it is not appropriate, it shifts the process to S280.

In S270, the tool control unit 61 determines that the stored content of the specific DTC transmitted from the ECU 10 is appropriate. Then, the tool control unit 61 stores the determination result in the memory 72, and ends the requesting side recognition process. As a result, the tool control unit 61 causes the inspection tool 3 to recognize that the stored content of the specific DTC transmitted from the ECU 10 is appropriate, for example, based on the determination result.

In this step, the tool control unit 61 may be configured to display information indicating that the stored contents of the specific DTC are appropriate on the display 33.
In S280, the tool control unit 61 determines that the stored content of the specific DTC transmitted from the ECU 10 is not appropriate. Then, the tool control unit 61 stores the determination result in the memory 72, and ends the requesting side recognition process. As a result, the tool control unit 61 causes the inspection tool 3 to recognize that the stored content of the specific DTC transmitted from the ECU 10 is not appropriate, for example, based on the determination result.

In this step, the tool control unit 61 may be configured to display information indicating that the stored contents of the specific DTC are not appropriate on the display 33.
[1-3. effect]
According to the first embodiment described in detail above, the following effects are obtained.

(1a) The failure detection system 1 includes a vehicle-side recognition unit 57 in the ECU 10. The vehicle-side recognition unit 57 acquires additional information associated with the specific DTC that is the target of the read request, and determines whether or not the stored content of the specific DTC is appropriate based on the additional information. .. When the ECU 10 determines that the stored content of the specific DTC is not appropriate based on the additional information, the ECU 10 causes the inspection tool 3 to recognize that the stored content of the specific DTC is not appropriate.

As a result, the inspection tool 3 can be made to recognize that the stored content of the specific DTC that is the target of the read request is not appropriate. Then, for example, by configuring the inspection tool 3 so that the vehicle inspection is not performed when the stored content of the specific DTC is not appropriate, it is possible to prevent the vehicle from passing the vehicle inspection by mistake.

(1b) The failure detection system 1 includes a request side recognition unit 76 in the inspection tool 3. The tool control unit 61 acquires from the ECU 10 the stored contents of the specific DTC that is the target of the read request and the additional information associated with the specific DTC that is the target of the read request in the request side recognition unit 76. It is determined whether or not the stored contents of the specific DTC are appropriate based on the additional information. When the tool control unit 61 determines that it is not appropriate, the tool control unit 61 causes the inspection tool 3 to recognize that the stored content of the specific DTC is not appropriate.

As a result, the inspection tool 3 can prevent the inspection tool 3 from passing the vehicle inspection by mistake, for example, by not passing the vehicle inspection when it is recognized that the specific DTC is not appropriate.
(1c) The failure detection system 1 includes both a vehicle-side recognition unit 57 of the ECU 10 and a request-side recognition unit 76 of the inspection tool 3. That is, both the vehicle side recognition unit 57 and the request unit 75 determine whether or not the stored content of the specific DTC is appropriate based on the additional information.

As a result, even if an abnormality occurs in which the stored content of the specific DTC is rewritten in the middle of the communication path between the ECU 10 and the inspection tool 3, the rewritten stored content of the specific DTC in the inspection tool 3 is appropriate. It is possible to judge whether or not. Therefore, it is possible to prevent the vehicle from passing the vehicle inspection by mistake based on the rewritten stored contents of the specific DTC.

(1d) The additional information storage unit 56 may be configured to acquire and store the diagnosis execution information as additional information. At least one of the vehicle-side recognition unit 57 and the request-side recognition unit 76 may be configured to use the diagnosis execution information for determining whether or not the stored content of the specific DTC is appropriate. As a result, it is possible to appropriately determine whether or not the stored content of the specific DTC is appropriate based on whether or not the abnormality diagnosis by the diagnosis execution unit 54 has been executed.

(1e) Elapsed time information may be used as diagnosis execution information. At this time, the ECU 10 may include an initialization unit 51 and an elapsed time generation unit 52. At least one of the vehicle side recognition unit 57 and the request side recognition unit 76 determines that the stored content of the specific failure code is not appropriate when the elapsed time information represents a time shorter than a predetermined elapsed time threshold value. It may be configured.

The elapsed time threshold value described above may be set to a time longer than the time required for diagnosis. Further, the above-mentioned elapsed time threshold value may be set to the time required for diagnosis.
As a result, it is possible to appropriately determine whether or not the stored content of the specific DTC is appropriate based on whether or not the abnormality diagnosis by the diagnosis execution unit 54 has been executed.

(1f) The additional information storage unit 56 may be configured to store state information as additional information. Even if at least one of the vehicle side recognition unit 57 and the request side recognition unit 76 is configured to determine that the stored content of the specific DTC is not appropriate when the state information indicates that the state of the ECU 10 is abnormal. Good. As a result, it is possible to appropriately determine whether or not the stored content of the specific DTC is appropriate according to the state of the ECU 10.

(1g) The information output unit 58 outputs the stored contents of the specific DTC and additional information to the inspection tool 3 when the predetermined output conditions are satisfied. As a result, when the output condition is satisfied, the inspection tool 3 can also determine whether or not the stored content of the specific DTC is appropriate based on the additional information.

(1h) The information output unit 58 may be configured to encrypt and output the stored contents and additional information of the specific DTC based on the VIN code which is the identification information unique to the vehicle. The inspection tool 3 may be configured to decode the stored contents and additional information of the specific DTC output from the ECU 10 based on the VIN code. The VIN code is identification information unique to the vehicle, in other words, identification information unique to the ECU 10 mounted on the vehicle.

If the ECU of a vehicle that has not been inspected and has already passed the inspection is improperly installed in place of the ECU that was installed in the vehicle that has not been inspected. , Vehicles that have not been inspected may accidentally pass the inspection.

In the present embodiment, when the ECU is improperly mounted on the vehicle in this way, the VIN code recognized by the improperly mounted ECU and the VIN code recognized by the inspection tool 3 are different, so that the inspection tool 3 is used. , It is not possible to decrypt the stored contents and additional information of the specific DTC encrypted by the improperly mounted ECU. As a result, when the ECU is improperly mounted on the vehicle, it is possible to prevent the vehicle from passing the vehicle inspection by mistake based on the stored contents of the specific DTC.

(1i) The information output unit 58 sends the inspection tool 3 to the inspection tool 3 when it is determined that the stored content of the specific DTC is appropriate, with the above-mentioned output condition that the stored content of the specific DTC is determined to be appropriate. It may be configured to output the stored contents of the specific DTC and additional information. As a result, the ECU 10 can transmit the appropriate stored contents of the specific DTC to the inspection tool 3. For example, the requesting side recognition unit 76 can be omitted from the first embodiment and the inspection tool 3, and the configuration of the inspection tool 3 can be simplified.

(1j) When the vehicle side recognition unit 57 determines that the stored content of the specific DTC is not appropriate, the vehicle side recognition unit 57 gives a no response or a negative response to the inspection tool 3, so that the stored content of the specific DTC is stored in the inspection tool 3. It may be configured to recognize that it is not appropriate. The inspection tool 3 may be configured to recognize that the stored content of the specific DTC targeted for the read request is not appropriate when there is no response or negative response from the ECU 10 after outputting the read request. ..

As a result, it is possible to prevent the vehicle from passing the vehicle inspection by mistake based on the stored contents of the specific DTC that is not appropriate.
[2. Second Embodiment]
Since the basic configuration of this embodiment is the same as that of the first embodiment, the differences will be described below. It should be noted that the same reference numerals as those in the first embodiment indicate the same configuration, and the preceding description will be referred to.

In the first embodiment described above, in the failure detection system 1, the ECU 10 includes the vehicle side recognition unit 57, and the inspection tool 3 includes the request side recognition unit 76. On the other hand, the second embodiment is different from the first embodiment in that the inspection tool 3 does not include the requesting side recognition unit 76.

Similar to the first embodiment, the ECU 10 includes an initialization unit 51-diagnosis execution unit 54, a code storage unit 55, an additional information storage unit 56, a vehicle-side recognition unit 57, and an information output unit 58. As in the first embodiment, the information output unit 58 also determines that the stored content of the specific DTC is appropriate, subject to the above-mentioned output condition that the stored content of the specific DTC is determined to be appropriate. In this case, the inspection tool 3 is configured to output the stored contents of the specific DTC and additional information.

In the present embodiment, the tool control unit 61 does not include the recognition determination unit 76. For example, in the request side recognition process executed by the tool control unit 61, S250 and S260 in the flowchart shown in FIG. 9 may be omitted. That is, when there is a response from the ECU 10, the tool control unit 61 determines that the stored content of the transmitted DTC is appropriate, and performs a vehicle inspection using the stored content of the transmitted DTC as it is. May be done.

As a result, the same effect as in (1a) above can be obtained, and the requesting side recognition unit 76 can be omitted from the inspection tool 3, so that the configuration of the inspection tool 3 can be simplified. As described above, in the failure detection system 1, at least one of the ECU 10 and the inspection tool 3 may include a recognition unit, that is, a vehicle-side recognition unit 57 in the present embodiment.

[3. Third Embodiment]
In the first embodiment described above, in the failure detection system 1, the ECU 10 includes the vehicle side recognition unit 57, and the inspection tool 3 includes the request side recognition unit 76. On the other hand, the third embodiment is different from the first embodiment in that the ECU 10 does not include the vehicle side recognition unit 57.

In the present embodiment, the ECU 10 does not include the vehicle side recognition unit 57. For example, in the vehicle-side recognition process executed by the ECU 10, S110 and S160 in the flowchart shown in FIG. 8 may be omitted. That is, in the ECU 10, the information output unit 58 uses the output of the read request as the above-mentioned output condition, and whenever the read request is output, the inspection tool 3 always checks the stored contents and additional information of the specific DTC. It may be configured to output to.

The inspection tool 3 is configured in the same manner as in the first embodiment. That is, in the inspection tool 3, the requesting side recognition unit 76 determines whether or not the stored content of the specific DTC is appropriate based on the additional information output from the ECU 10, and if it is determined that it is not appropriate, the inspection tool 3. 3 may be configured to recognize that the stored content of the specific DTC is not appropriate. The tool control unit 61 may be configured to execute the same processing as the requesting side recognition processing of the first embodiment shown in FIG.

Further, in the inspection tool 3, when it is determined that the stored content of the specific DTC is not appropriate, the tool control unit 61 may be configured not to perform the vehicle inspection using the stored content of the specific DTC.

As a result, the same effect as in (1b) above can be obtained, and the vehicle side recognition unit 57 can be omitted from the ECU 10, so that the processing load on the ECU 10 can be reduced. As described above, in the failure detection system 1, at least one of the ECU 10 and the inspection tool 3 may include a recognition unit, that is, a recognition determination unit 76 in the present embodiment.

[4. Other embodiments]
Although the embodiments of the present disclosure have been described above, the present disclosure is not limited to the above-described embodiments, and can be implemented in various modifications.

(4a) In the above embodiment, elapsed time information, which is diagnostic execution information, specifically, elapsed time after initialization is used as additional information. However, the present disclosure is not limited to this.

For example, the diagnosis execution information may be elapsed time information other than the elapsed time after initialization. For example, the elapsed time information may be a time stamp representing a time, or may be various travel histories.

Further, for example, the diagnosis execution information may be information representing the diagnosis result by the diagnosis execution unit 54, that is, a normal flag, an abnormality flag, or itself. This is because it is clear that the abnormality diagnosis has been executed because the normal flag and the abnormality flag are stored. As described above, when the abnormality diagnosis is completed and the diagnosis result is stored, the code storage unit 55 is activated. That is, since the information representing the diagnosis result is stored, the specific DTC is stored after the abnormality diagnosis is executed, or the specific DTC is not stored after the abnormality diagnosis is executed. This is because it is clear.

In this case, both the abnormality flag and the normal flag are used as the diagnosis execution information, and the code storage unit 55 may store these flags as the diagnosis execution information, that is, additional information in the specific DTC storage area 141. At least one of the vehicle side recognition unit 57 and the request side recognition unit 76 determines that the stored contents of the specific DTC are not appropriate when these flags as diagnosis execution information are not stored in the specific DTC storage area 141. It may be configured in. Then, the initialization unit 51 may be configured so that at least the specific DTC storage area 141 is erased.

The additional information storage unit 56 may be configured to acquire and store various types of diagnosis execution information as additional information.
(4b) In the above embodiment, the number of on / off times is used as the traveling history. However, the travel history is not limited to the number of on / off times.

For example, the travel history may be the cumulative operating time representing the time when the ECU 10 is turned on after the ECU 10 is initialized. Further, for example, the traveling history may be an engine operating time representing a time when the engine ECU that controls the engine is turned on after the ECU 10 is initialized. Further, for example, the travel history may be the number of trips measured as one trip from the time when the engine ECU is turned on to the time when the engine ECU is turned on after the ECU 10 is initialized. Further, for example, the travel history may be the travel distance of the vehicle.

The elapsed time generation unit 52 may be configured to generate such elapsed time information.
(4c) In the above embodiment, the memory abnormality information is used as the state information. However, the state information is not limited to the memory abnormality information.

For example, the state information may be information indicating that the ECU 10 has been removed from the vehicle. This is because if the ECU 10 has been removed from the vehicle, there is a possibility that an abnormality has occurred in the ECU 10. Specifically, when the ECU 10 is communicating according to the CAN via the communication line 16 in the vehicle, an abnormality is detected in the communication according to the CAN by removing the ECU 10 from the communication line 16. CAN is an abbreviation for Controller Area Network and is a registered trademark. The monitoring unit 53 may be configured to detect such an abnormality and generate state information indicating that the abnormality has occurred in the ECU 10 when the abnormality is detected.

Also, for example, the state information can be information indicating that the vehicle has been activated by an invalid key. This is because if the vehicle is activated by an illegal key, there is a possibility that an abnormality has occurred in the ECU 10 mounted on the vehicle. Specifically, when the vehicle is equipped with an immobilizer, an abnormality is detected in the immobilizer when the vehicle is activated by an illegal key. The monitoring unit 53 may be configured to detect such an abnormality and generate state information indicating that the abnormality has occurred in the ECU 10 when the abnormality is detected.

Further, for example, the state information may be information indicating that an abnormality has occurred in the writing function or reading function of the SRAM 14 by the ECU 10. Specifically, when the specific DTC is stored in a plurality of locations in the SRAM 14 and the ECU 10 has a function of detecting whether or not the specific DTCs stored in the plurality of locations match (hereinafter, mirror check function). An abnormality is detected when the specific DTCs stored in a plurality of locations do not match. The monitoring unit 53 may be configured to detect such an abnormality and generate state information indicating that the abnormality has occurred in the ECU 10 when the abnormality is detected.

Further, for example, the state information may be information indicating that an unauthorized access has been made to the protected area provided in the microcomputer 11 of the ECU 10. The microcomputer 11 is configured to detect that an unauthorized access has been made to the protected area of the microcomputer 11. This is because if there is an unauthorized access to the protected area of the microcomputer 11, there is a possibility that an abnormality has occurred in the ECU 10. The ECU 10 may be configured to store the specific DTC in the protected area provided in the microcomputer 11.

The monitoring unit 53 may be configured to detect such an abnormality and generate state information indicating that the abnormality has occurred in the ECU 10 when the abnormality is detected.
(4d) The vehicle-side recognition unit 57 is configured to make the inspection tool 3 recognize that the stored content of the specific DTC is not appropriate by making no response to the inspection tool 3, but the limitation is limited to this. It is not something that is done. The vehicle-side recognition unit 57 may be configured to make the inspection tool 3 recognize that the stored content of the specific DTC is not appropriate by giving a negative response to the inspection tool 3.

In this case, for example, the inspection tool 3 may be configured to stop the vehicle inspection by the specific DTC by determining that the stored content of the specific DTC in the ECU 10 is not appropriate when receiving a negative response.

(4e) The additional information may be information indicating whether or not the vehicle has a one-to-one correspondence ECU 10, that is, the vehicle-specific ECU 10 corresponding to the vehicle. In the above embodiment, the stored contents and additional information of the specific DTC transmitted from the ECU 10 are encrypted by the VIN code which is the unique identification information, so that the stored contents of the specific DTC transmitted from the ECU 10 are stored by the ECU 10 unique to the vehicle. It represented that it was a thing. However, the unique identification information is not limited to this. Any information unique to the vehicle other than the VIN code may be used as the unique identification information.

(4f) In the above embodiment, the vehicle control device 2 includes one ECU 10, but the vehicle control device 2 is not limited to this. The vehicle control device 2 may include a plurality of ECUs 10. In this case, each of the plurality of ECUs 10 may be connected to the communication line 16 and may be able to communicate with each other according to a communication protocol such as CAN. The plurality of ECUs 10 may execute vehicle control predetermined for each ECU.

(4g) In the above embodiment, the ECU 10 and the inspection tool 3 are connected by a cable 40 to enable communication, but the present invention is not limited to this. For example, the ECU 10 and the inspection tool 3 may be configured to be able to communicate wirelessly.

(4h) In the above embodiment, the inspection tool 3 is configured to determine the pass / fail of the vehicle inspection, but the present invention is not limited to this. For example, the server 4 may be configured to determine the pass / fail of the vehicle inspection. In this case, the server 4 may be configured to acquire the specific DTC read from the ECU 10 by the inspection tool 3 and determine the pass / fail of the vehicle inspection based on the specific DTC information using the specific DTC. Further, the server 4 may be configured to output the determination result to the inspection tool 3.

(4i) A plurality of functions possessed by one component in the above embodiment may be realized by a plurality of components, or one function possessed by one component may be realized by a plurality of components. .. Further, a plurality of functions possessed by the plurality of components may be realized by one component, or one function realized by the plurality of components may be realized by one component. Further, a part of the configuration of the above embodiment may be omitted. In addition, at least a part of the configuration of the above embodiment may be added or replaced with the configuration of the other above embodiment.

(4j) In addition to the above-mentioned failure detection system 1, vehicle control device 2, ECU 10, inspection tool 3, and tool control unit 61, a program for operating the ECU 10, a semiconductor memory in which this program is recorded, and the like are non-transitional actual conditions. The present disclosure can also be realized in various forms such as a recording medium, a program for operating the tool control unit 61, a non-transitional actual recording medium such as a semiconductor memory in which this program is recorded, and a failure detection method.

In the above embodiment, the ECU 10 corresponds to the vehicle electronic control device, the inspection tool 3 corresponds to the request device, and the vehicle side recognition unit 57 and the request side recognition unit 76 correspond to the recognition unit. Further, the specific DTC corresponds to the specific failure code.

1 Failure detection system, 3 Inspection tool, 10 ECU, 14 SRAM, 54 Diagnosis execution unit, 55 Code storage unit, 56 Additional information storage unit, 57 Vehicle side recognition unit, 76 Request side recognition unit.

Claims (15)

A vehicle electronic control device (10) having a failure storage device (14) mounted on a vehicle and storing a failure code indicating an abnormality of the vehicle, and a request to output a read request for reading the failure code to the vehicle electronic control device. A failure detection system (1) including a device (3).
The vehicle electronic control unit is
A code storage unit (55) that acquires a diagnosis result from a diagnosis execution unit (54) that executes an abnormality diagnosis of the vehicle and stores the failure code in the failure storage device based on the diagnosis result.
An additional information storage unit (56) that acquires additional information for indicating whether or not the storage content of the failure code in the failure storage device is appropriate and stores the additional information in association with the failure code.
With
The failure detection system
The additional information associated with the failure code that is the target of the read request is acquired, and based on the additional information, it is determined whether or not the stored content of the failure code is appropriate, and it is determined that the additional information is not appropriate. A recognition unit (57, 76) that causes the requesting device to recognize that the stored content of the failure code is not appropriate.
With
The failure code is a failure detection system that is a specific failure code used for determining the inspection of the vehicle. The failure detection system according to claim 1.
The additional information storage unit acquires and stores the diagnosis execution information indicating whether or not the abnormality diagnosis is executed and the specific failure code is stored as the additional information.
The recognition unit is a failure detection system that uses the diagnosis execution information to determine whether or not the stored content of the specific failure code is appropriate. The failure detection system according to claim 2.
The diagnosis execution information is information representing the diagnosis result by the diagnosis execution unit.
The recognition unit is a failure detection system that determines that the stored content of the specific failure code is not appropriate when the diagnosis execution information is not stored by the additional information storage unit. The failure detection system according to claim 2 or 3.
The diagnosis execution information is elapsed time information representing the elapsed time since the vehicle electronic control unit was initialized.
The recognition unit determines that the stored content of the specific failure code is not appropriate when the elapsed time information represents a time shorter than a predetermined elapsed time threshold value.
Failure detection system. The failure detection system according to any one of claims 1 to 4.
The additional information storage unit stores state information indicating whether or not the state of the electronic control unit is abnormal as the additional information.
When the state information indicates that the state of the electronic control unit is abnormal, the recognition unit determines that the stored content of the specific failure code is not appropriate.
Failure detection system. The failure detection system according to any one of claims 1 to 5.
The electronic control unit is
An information output unit (58) that outputs the stored contents of the specific failure code and the additional information to the requesting device when a predetermined output condition is satisfied.
Fault detection system with. The failure detection system according to claim 6.
The information output unit is a failure detection system that encrypts and sends the stored contents of the specific failure code and the additional information based on the identification information unique to the vehicle. The failure detection system according to claim 6 or 7.
The information output unit uses the output of the read request as the output condition, and when the read request is output, the failure detection system outputs the stored contents of the specific failure code and the additional information. The failure detection system according to claim 6 or 7.
The vehicle electronic control device is a failure detection system including a vehicle side recognition unit (57) as the recognition unit. The failure detection system according to claim 9.
The information output unit sends the requesting device when it is determined that the stored content of the specific failure code is appropriate, with the output condition that the stored content of the specific failure code is determined to be appropriate. A failure detection system that outputs the stored contents of the specific failure code and the additional information. The failure detection system according to claim 9 or 10.
When the vehicle side recognition unit determines that the stored content of the specific failure code is not appropriate, the vehicle-side recognition unit makes a no response or a negative response to the requesting device, thereby causing the requesting device to store the stored content of the specific failure code. A failure detection system that recognizes that is not appropriate. The failure detection system according to claim 11.
The requesting device is
A failure detection system that recognizes that the stored content of the specific failure code that is the target of the read request is not appropriate when there is no response or a negative response from the electronic control unit after outputting the read request. The failure detection system according to any one of claims 1 to 12.
The requesting device includes a requesting side recognition unit (76) as the recognition unit.
The requesting side recognition unit determines whether or not the stored content of the failure code is appropriate based on the additional information output from the electronic control unit, and when it is determined that it is not appropriate, the requesting device is notified. A failure detection system that recognizes that the stored contents of the failure code are not appropriate. The reading from a requesting device (3) which has a failure storage device (14) mounted on a vehicle and stores a failure code indicating an abnormality of the vehicle and outputs a reading request for reading the failure code to the vehicle electronic control unit. A vehicle electronic control unit that receives a request
The vehicle electronic control unit is
A code storage unit (55) that acquires a diagnosis result from a diagnosis execution unit (54) that executes an abnormality diagnosis of the vehicle and stores the failure code in the failure storage device based on the diagnosis result.
An additional information storage unit (56) that acquires additional information for indicating whether or not the storage content of the failure code in the failure storage device is appropriate and stores the additional information in association with the failure code.
With
One of the vehicle electronic control unit and the required device
The additional information associated with the failure code that is the target of the read request is acquired, and based on the additional information, it is determined whether or not the stored content of the failure code is appropriate, and it is determined that the additional information is not appropriate. A recognition unit (57, 76) that causes the requesting device to recognize that the stored content of the failure code is not appropriate.
With
The failure code is a vehicle electronic control unit which is a specific failure code used for determining the inspection of the vehicle. It is a request device (3) that outputs a read request for reading the failure code to a vehicle electronic control device (10) having a failure storage device (14) mounted on the vehicle and storing a failure code indicating an abnormality of the vehicle. hand,
The vehicle electronic control unit is
A code storage unit (55) that acquires a diagnosis result from a diagnosis execution unit (54) that executes an abnormality diagnosis of the vehicle and stores the failure code in the failure storage device based on the diagnosis result.
An additional information storage unit (56) that acquires additional information for indicating whether or not the storage content of the failure code in the failure storage device is appropriate and stores the additional information in association with the failure code.
With
One of the requesting device and the vehicle electronic control unit
The additional information associated with the failure code that is the target of the read request is acquired, and based on the additional information, it is determined whether or not the stored content of the failure code is appropriate, and it is determined that the additional information is not appropriate. A recognition unit (57, 76) that causes the requesting device to recognize that the stored content of the failure code is not appropriate.
With
The failure code is a request device that is a specific failure code used for determining the inspection of the vehicle.

Images