JP2020083139A - Vehicle electronic control device and diagnostic system - Google Patents

Abstract

To provide a vehicular electronic control device and a diagnostic system capable of suitably performing inspection such as vehicle inspection by using a DTC.SOLUTION: A vehicle electronic control device 5 includes a first diagnosis section 27, a second diagnosis section 29 and a vehicle storage section 23. The first diagnosis section 27 diagnoses an abnormality of a specific configuration of a vehicle 3 on the basis of a first diagnosis rule defining details of a diagnosis for detecting an abnormality related to the specific configuration of the vehicle 3. The second diagnosis section 29 diagnoses an abnormality of the specific configuration on the basis of a second diagnosis rule that is different from the first diagnosis rule and defines details of the diagnosis for detecting an abnormality related to the specific configuration. When the first diagnosis section 27 detects an abnormality of the specific configuration, the vehicle storage section 23 stores a first failure code indicating the abnormality, and when the second diagnosis section 29 detects an abnormality of the specific configuration, the vehicle storage section stores a second failure code indicating the abnormality.SELECTED DRAWING: Figure 4

Description

The present disclosure relates to a vehicle electronic control device mounted on a vehicle and a diagnostic system including the vehicle electronic control device and an inspection tool.

BACKGROUND ART Conventionally, as a function of an on-vehicle electronic control device (that is, a vehicle electronic control device), an OBD is known, for example, as described in Patent Document 1 below. OBD is an abbreviation for On-board Diagnostics. This OBD detects that some kind of abnormality has occurred in various sensors, actuators, etc. mounted on the vehicle, and records a failure code corresponding to the abnormality. Hereinafter, the failure code is also referred to as DTC. DTC is an abbreviation for Diagnostic Trouble Code.

Further, in recent years, in order to detect an exhaust gas-related abnormality of a vehicle, various laws and regulations (that is, laws and regulations) defining OBD regarding exhaust gas have been established in foreign countries and in Japan. Then, according to this regulation (that is, OBD regulation), various DTCs indicating exhaust gas-related abnormality are set, and the abnormality diagnosis logic when diagnosing abnormality and the judgment value (that is, threshold value) when diagnosing abnormality are also set. It is set.

JP-A-5-172706

The above-mentioned DTC indicates a past abnormality such as exhaust gas related to the vehicle. Therefore, in the future, for example, in the automobile inspection registration system (that is, vehicle inspection), it is possible to use this DTC for the inspection of the state of the vehicle, but it is necessary to sufficiently examine it.

Then, when the case where DTC is used for vehicle inspection as described below was examined, it was found by the inventor of the present application that the following problems exist.
For example, among DTCs, a predetermined DTC indicating a failure that does not meet the safety standards of the Road Transport Vehicle Act is defined as a specific DTC, and when this specific DTC is read by an inspection tool (that is, a scan tool), the vehicle inspection is rejected. It is possible. That is, when the specific DTC is stored in the vehicle electronic control unit, it is possible to make the vehicle inspection fail.

As described above, when the DTC is used for the vehicle inspection, for example, the DTC set by the OBD regulation may be adopted as the specific DTC used for the vehicle inspection. In addition, below, DTC set by the OBD regulation may be described as regulation DTC.

By the way, since the regulation DTC and the specific DTC are originally DTC defined by separate regulations, when a standard higher than the standard of the regulation OBD (that is, a strict standard) is required in the future as a standard for the specific DTC, It is considered that the regulation DTC and the specific DTC need to be adjusted.

For example, as shown in FIG. 2A, when considering the output voltage of a predetermined sensor, for example, the criterion for the abnormality determination of the regulation DTC (for example, OBD regulation threshold) is more than the criterion for the abnormality determination of the specific DTC (for example, the safety criterion threshold). When it is low, that is, when the OBD regulation threshold value is stricter than the safety criterion threshold value, it seems that there is no problem even if the regulation DTC is adopted as the specific DTC. In addition, here, when the output voltage is higher than the threshold value, it is determined to be abnormal.

However, for example, as shown in FIG. 2B, when the OBD regulation threshold value is higher than the security reference threshold value, that is, when the OBD regulation threshold value is not stricter than the security reference threshold value, if the regulation DTC is adopted as the specific DTC, there is a problem. Seems like there is. In other words, in the case of vehicle inspection, it is necessary to determine that the output voltage is abnormal when the output voltage reaches the safety reference threshold. However, if a non-strict OBD regulation threshold is adopted as the safety reference threshold, there is an abnormality related to vehicle inspection. However, there is a possibility that it may be determined that there is no abnormality.

One aspect of the present disclosure is to provide an electronic control device for a vehicle and a diagnostic system capable of suitably performing vehicle inspection and the like by utilizing DTC.

a) One aspect of the present disclosure is a vehicle electronic control unit (5) mounted on a vehicle (3), which includes a first diagnosis unit (27), a second diagnosis unit (29), and a storage unit ( 23) and.
The first diagnostic unit diagnoses an abnormality of a specific configuration of the vehicle based on a first diagnostic rule that defines the content of the diagnosis for detecting an abnormality related to a specific configuration of the vehicle (that is, a diagnosis target). ..

The second diagnostic unit defines a second diagnostic rule different from the first diagnostic rule that defines the content of the diagnosis for detecting an abnormality regarding the specific configuration (that is, the diagnosis target of the first diagnostic unit). Based on this, the diagnosis of the abnormality of the specific configuration is performed.

The storage unit stores a first failure code indicating the abnormality when the first diagnostic unit detects an abnormality of the specific configuration, and the second diagnostic unit detects the abnormality of the specific configuration. If so, the second failure code indicating the abnormality is stored.

According to such a configuration, when an abnormality of a specific configuration is detected by the first diagnostic unit, the first failure code indicating the abnormality is stored and the second diagnostic unit performs the specific configuration. When the abnormality is detected, the second failure code indicating the abnormality is stored, so that it is possible to deal with each failure code.

In other words, the first failure code and the first failure code are stored in the storage unit on the basis of the result of the diagnosis performed on the same diagnosis target based on different diagnosis rules (for example, different abnormality diagnosis logic and different thresholds used for abnormality determination). The second failure code is stored. Therefore, the first failure code and/or the second failure code can be read from the storage unit as needed, and thus the failure code can be obtained according to the requested content of the diagnosis result (for example, the diagnosis level). ..

That is, since the diagnosis result according to the request content can be acquired, it is possible to perform an appropriate response such as performing repair or determining whether the vehicle inspection is successful or not according to the diagnosis result.
For example, by selecting and acquiring a specific DTC from the vehicle electronic control unit using an inspection tool, the state of the vehicle can be surely determined, so it is possible to reliably determine whether the vehicle inspection has passed or failed. Is possible.

b) Another aspect of the present disclosure is a diagnostic system (13) including a vehicle electronic control unit and an inspection tool.
This diagnostic system includes the vehicle electronic control unit described above and an inspection tool (7) that is connected to the vehicle electronic control unit and communicates with the vehicle electronic control unit. Further, the vehicle electronic control unit has a device side connector (25), and the inspection tool has a tool side connector (41).

According to the connection state (for example, an indirect or direct connection state) between the device-side connector and the tool-side connector, this diagnostic system provides a first failure code and/or a signal from the vehicle electronic control unit to the inspection tool side. Alternatively, it is configured to output the second failure code.

With such a configuration, the same effect as that of the above-described one aspect of the present disclosure can be obtained.
c) Yet another aspect of the present disclosure is a diagnostic system (13) including a vehicle electronic control unit and an inspection tool.

This diagnostic system includes the vehicle electronic control device described above and an inspection tool that is connected to the vehicle electronic control device and communicates with the vehicle electronic control device.
The diagnostic system is based on a control signal transmitted from the inspection tool side to the vehicle electronic control device side and instructing the output of the first failure code and/or the second failure code. Is output to the inspection tool side from the first failure code and/or the second failure code.

With such a configuration, the same effect as that of the above-described one aspect of the present disclosure can be obtained.
It should be noted that the reference numerals in parentheses described in this column and in the claims indicate the correspondence with the specific means described in the embodiments described below as one aspect, and do not indicate the technical scope of the present disclosure. It is not limited.

The block diagram which shows the vehicle inspection system in 1st Embodiment. Explanatory drawing which shows the relationship between a security standard threshold value and an OBD regulation threshold value. Explanatory drawing which shows the relationship between regulation DTC and specific DTC. The block diagram which shows the vehicle electronic control unit of 1st Embodiment. Explanatory drawing which shows the identifier of a 1st failure code and a 2nd failure code. The block diagram which shows the inspection tool of 1st Embodiment. The sequence diagram which shows the procedure of communication between the vehicle electronic control unit and inspection tool of 1st Embodiment. The flowchart which shows the process (1) of the vehicle electronic control apparatus of 1st Embodiment. The flowchart which shows the process (2) of the vehicle electronic control apparatus of 1st Embodiment. The flowchart which shows the process of the vehicle electronic control apparatus of 2nd Embodiment.

Embodiments of the present disclosure will be described below with reference to the drawings.
[1. First Embodiment]
[1-1. overall structure]
First, an overall system (that is, a vehicle inspection system) including the diagnostic system of the first embodiment will be described.

As shown in FIG. 1, a vehicle inspection system 1 according to the first embodiment is an electronic control unit (that is, a vehicle electronic control unit) 5 mounted on a vehicle 3 and an inspection electrically connected to the vehicle electronic control unit 5. The tool 7 and the management server 9 connected to the inspection tool 7 via the Internet are provided. In the following, the electronic control unit may be referred to as an ECU.

Here, an example is shown in which the vehicle ECU 5 and the inspection tool 7 are connected by the cable 11, but they may be connected by wireless. The diagnostic system 13 is configured to include the vehicle ECU 5 and the inspection tool 7.

In the vehicle inspection system 1 described above, processing for vehicle inspection and the like are performed as follows.
First, of the DTCs that are the failure codes indicating the abnormality of the vehicle 3, a predetermined DTC indicating a failure that does not satisfy the safety standard of the Road Transport Vehicle Act is defined as a specific DTC. The specific DTC corresponds to the second failure code, for example.

When an abnormality corresponding to the specific DTC is detected in the vehicle 3, the specific DTC is stored in the vehicle ECU 5. Then, when the specific DTC is read by the inspection tool 7 from the vehicle ECU 5 during the vehicle inspection, the vehicle inspection is rejected.

That is, when the DTC provided with the safety standard is set as the specific DTC and the specific DTC is stored in the vehicle ECU 5, the vehicle inspection is rejected.
Information such as the specific DTC and its version, that is, specific DTC information that is information regarding the specific DTC is stored in the management server 9 of the specific DTC management mechanism. At the time of vehicle inspection or the like, the inspection tool 7 accesses the management server 9 to acquire and update the specific DTC information, and then the inspection tool 7 inspects the vehicle 3 for occurrence of the specific DTC. ..

In addition to the specific DTC described above, there is an OBD regulation (for example, J-OBDII) that is a regulation of exhaust emission-related laws and the like in order to detect an abnormality relating to exhaust gas. In the first embodiment, this OBD regulation is provided. The DTC set in step (i.e., the regulation DTC) is also stored in the vehicle ECU 5. The regulation DTC corresponds to, for example, the first failure code.

Therefore, the state of the vehicle 3 can be diagnosed by reading the regulation DTC from the vehicle ECU 5 separately from the specific DTC.
For example, as shown in FIG. 2A, when considering the output voltage of a predetermined sensor, the criterion for abnormality determination of the regulation DTC (for example, OBD regulation threshold value) is lower than the criterion for abnormality determination of the specific DTC (for example, safety criterion threshold value). The case (that is, the case where the criterion is strict) is considered. In this case, it seems that there is no problem even if the regulation DTC is adopted as the specific DTC. In addition, here, when the output voltage is higher than the threshold value, it is determined to be abnormal.

On the other hand, for example, as shown in FIG. 2B, the OBD regulation threshold value may be higher than the security reference threshold value. In this case, however, the security reference threshold value is stricter than the OBD regulation threshold value. An abnormality is diagnosed based on the security reference threshold.

In the first embodiment, as shown in FIG. 3, among many DTCs, for example, a predetermined DTC indicating an exhaust gas-related abnormality is set as the regulation DTC, and the predetermined DTC of the regulation DTC is set as the specific DTC. It is set.

[1-2. Each configuration]
Next, each component of the diagnostic system 13 and the like of the first embodiment will be described in detail.
<Vehicle electronic control unit>
As shown in FIG. 4, the vehicle ECU 5 is an electronic control unit centered on a microcomputer that constitutes the vehicle arithmetic processing unit 21, and some abnormality occurs in various sensors and actuators mounted on the vehicle while the vehicle is running. It has an OBD function to detect that.

Specifically, the vehicle ECU 5 includes a vehicle calculation processing unit 21 that performs various calculations, a vehicle storage unit 23 that stores various data, a vehicle connector 25 that is a connection terminal to the outside, and the like. Although not shown, the vehicle calculation processing unit 21 is composed of a CPU, a ROM, a RAM, and the like. The vehicle connector 25 is connected to a connector (not shown) at one end of the cable 11.

The vehicle arithmetic processing unit 21 has a first diagnosis unit 27 and a second diagnosis unit 31 as a functional configuration realized by the CPU executing a program.
The first diagnosis unit 27 diagnoses the abnormality of the specific configuration, which is the target of detecting the abnormality, based on the first diagnostic rule that defines the content of the diagnosis. The specific configuration is a target (inspection target) for detecting an abnormality, such as various sensors and actuators mounted on a vehicle.

The second diagnostic unit 29 performs the same test on the inspection target of the first diagnostic unit 27 based on a second diagnostic rule (for example, a threshold value) that defines the content of the diagnosis and is different from the first diagnostic rule. Diagnose the target abnormality.

For example, when the inspection target of the first diagnosis unit 27 includes a certain sensor (for example, oxygen sensor), the inspection target of the second diagnosis unit 29 also includes the same sensor (for example, oxygen sensor). The first diagnostic unit 27 and the second diagnostic unit 29 perform the same examination target diagnosis, but can also perform other examination target diagnoses.

Here, the first diagnostic rule and the second diagnostic rule are respectively an abnormality diagnosis logic for detecting an abnormality of an inspection target and/or a threshold value used for determining whether or not there is an abnormality. Now, the threshold value will be described as an example.

The vehicle storage unit 23 is a rewritable nonvolatile memory such as a flash memory. When the first diagnostic unit 27 detects an abnormality in the inspection target, the vehicle storage unit 23 stores a first failure code indicating the abnormality. In addition, when the second diagnostic unit 29 detects an abnormality of the inspection target, the second failure code indicating the abnormality is stored.

Here, the second failure code is a failure code used for determining whether or not it meets the safety standards defined by the Road Transport Vehicle Act (that is, a vehicle inspection pass/fail determination), that is, a failure code corresponding to a specific DTC. is there. On the other hand, the first failure code is a failure code used for determining whether or not it conforms to a standard defined by a law different from the Road Transport Vehicle Law (for example, J-OBDII), that is, a failure code corresponding to the law DTC. Is.

The first failure code (that is, the regulation DTC) and the second failure code (that is, the specific DTC) are distinguished by the assigned identifier.
For example, as shown in FIG. 5, for example, when “P1234” is defined as the DTC indicating the abnormality of a certain sensor, even if the abnormality is detected by the first diagnosis unit 27, the second Even when the diagnosis unit 29 detects an abnormality, the corresponding DTC is “P1234”.

However, in the first embodiment, in order to distinguish between the first failure code (that is, the regulation DTC) and the second failure code (that is, the specific DTC), the minimum unit data at the time of data transmission/reception or storage is used. , An identifier is assigned. For example, as shown in FIG. 5A, the minimum unit of data including DTC is given an identifier of “01” indicating that the DTC is the regulation DTC immediately after “P1234” which is the DTC. ing. Further, as shown in FIG. 5B, the minimum unit of data including DTC is assigned an identifier of “02” indicating that the DTC is a specific DTC.

Therefore, the identifier immediately after the failure code can distinguish whether the failure code is the first failure code (that is, the regulation DTC) or the second failure code (that is, the specific DTC).
As a method for distinguishing between the first failure code and the second failure code, in addition to the method using the identifier, for example, a first storage area that stores only the first failure code and a second failure code There is a method of setting a second storage area for storing only the data. In this case, a desired type of failure code can be acquired by searching the storage area corresponding to the failure code to be acquired.

Further, for example, the first failure code and the second failure code are distinguished from each other by giving different codes to the first failure code and the second failure code instead of giving the above-mentioned identifier. May be separated.

<Inspection tool>
As shown in FIG. 6, the inspection tool 7 can be operated by a display 33 that performs various displays, a tool electronic control unit (that is, a tool ECU) 35 that controls the operation of the inspection tool 7, and a manual operation of an operator. The operation unit 37, the tool communication unit 39 for communicating with the management server 9, and the tool connector 41 to which the connector 12 (see FIG. 1) at the other end of the cable 11 is connected.

The tool ECU 35 includes a tool calculation processing unit 43 that performs various calculations and a tool storage unit 45 that stores various data.
Although not shown, the tool calculation processing section 43 is composed of a CPU, a ROM, a RAM and the like. In the tool calculation processing unit 43, for example, the management server 9 is requested to acquire and acquire the specific DTC information, or the vehicle ECU 5 is requested to acquire and acquire the specific DTC and the regulation DTC. Control.

The tool storage unit 45 is a rewritable nonvolatile memory such as a flash memory, and is configured to store the specific TDC information and the like acquired from the management server 9. Further, the specific DTC and the regulation DTC acquired from the vehicle ECU 5 are stored.

The tool communication unit 39 is a communication device that wirelessly communicates with the management server 9 via the Internet. The tool communication unit 39 is not normally connected to the management server 9, but is connected to the management server 9 when necessary by an operator's operation, and downloads the latest specific DTC information, for example.

In other words, the inspection tool 7 is a stand-alone type, and is not used by always connecting to the management server 9 online but using it offline. The inspection tool 7 may be always online and connected to the management server 9.

The various functions of the vehicle ECU 5 and the tool ECU 35 are realized by the CPU executing the programs stored in the non-transitional physical recording medium. In this example, the vehicle storage unit 23 and the tool storage unit 45 correspond to the non-transitional substantive recording medium storing the program. By executing this program, the method corresponding to the program is executed. The vehicle ECU 5 and the tool ECU 35 may each be configured by one microcomputer, or may be configured by a plurality of microcomputers.

Further, the method of realizing each processing executed by the vehicle ECU 5 and the tool ECU 35 is not limited to software, and one or a part of the functions thereof may be realized by using one or more hardware. 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.

[1-3. Control processing]
First, the outline of the processing performed by the vehicle inspection system 1 will be described.
As shown in FIG. 7, for example, at the time of vehicle inspection, the inspection tool 7 requests the vehicle ECU 5 to read (A) the specific DTC and/or the regulation DTC.

When the vehicle ECU 5 receives the read request for the specific DTC and/or the regulation DTC from the inspection tool 7, the vehicle ECU 5 transmits (B) the specific DTC and/or the regulation DTC to the inspection tool 7.

The inspection tool 7 reports the inspection result based on the specific DTC and/or the regulation DTC received from the vehicle ECU 5.
For example, when there is a specific DTC and/or a regulation DTC, the inspection result is displayed on, for example, the display 33 and stored in the tool storage unit 45.

Next, the processing performed by the vehicle ECU 5 will be specifically described.
<Process in vehicle ECU (1)>
This process (1) is a process that is normally executed in the vehicle ECU 5.

In the vehicle ECU 5, as shown in FIG. 8, in step 100, it is determined by OBD in the vehicle whether or not it is the timing for diagnosing the abnormality (that is, the diagnosis start timing). If an affirmative judgment is made here, the routine proceeds to step 110. On the other hand, if a negative judgment is made, this processing is once terminated.

As the diagnosis start timing, for example, a conventional diagnosis start timing set to detect each DTC can be adopted every predetermined period.
In step 110, diagnosis is performed based on the OBD regulation threshold value. That is, the abnormality diagnosis corresponding to the regulation DTC is performed by using the abnormality determination reference of the regulation DTC (for example, OBD regulation threshold value). That is, an inspection for detecting an abnormality corresponding to the regulation DTC is performed.

In the following step 120, it is determined whether or not an abnormality corresponding to the regulation DTC is detected as a result of the diagnosis based on the OBD regulation threshold value. If an affirmative judgment is made here, the routine proceeds to step 130, while if a negative judgment is made, the routine proceeds to step 140.

In step 130, since the abnormality corresponding to the regulation DTC is detected in step 120, the DTC storage according to the OBD regulation is executed. That is, the first failure code (that is, the regulation DTC) indicating that the abnormality corresponding to the regulation DTC is detected is stored in the vehicle storage unit 23. It should be noted that when the first failure code is stored, a predetermined identifier is also stored in order to indicate the first failure code. Then, it progresses to step 140.

On the other hand, in step 140, since the abnormality corresponding to the regulation DTC is not detected in step 120, the diagnosis based on the security reference threshold value is performed. That is, the abnormality diagnosis corresponding to the specific DTC is performed by using the abnormality determination reference of the specific DTC (for example, the safety reference threshold value). That is, the inspection for detecting the abnormality corresponding to the specific DTC is performed.

In the following step 150, it is determined whether or not an abnormality corresponding to the specific DTC is detected as a result of the diagnosis based on the security reference threshold value. If an affirmative judgment is made here, the routine proceeds to step 160, while if a negative judgment is made, this processing is once terminated.

In step 160, since the abnormality corresponding to the specific DTC is detected in step 150, the DTC storage based on the security standard is executed. That is, the second failure code (that is, the specific DTC) indicating that the abnormality corresponding to the specific DTC has been detected is stored in the vehicle storage unit 23, and the present processing is temporarily terminated. When the second failure code is stored, a predetermined identifier is also stored to indicate that it is the second failure code.

<Process (2) in vehicle ECU>
This process (2) is a process executed when the inspection tool 7 requests the vehicle ECU 5 to read out the DTC.

As shown in FIG. 9, the vehicle ECU 5 determines in step 200 whether or not there is a tool request. That is, it is determined whether the inspection tool 7 requests the vehicle ECU 5 to read the DTC. If an affirmative judgment is made here, the routine proceeds to step 210, while if a negative judgment is made, this processing is once terminated.

It should be noted that the operation of the operation unit 37, that is, the signal (that is, the control signal) input from the operation unit 37 can instruct whether to read the specific DTC or the law DTC.

In step 210, since there is a tool request, the reading method is recognized. For example, it recognizes whether the signal transmitted from the inspection tool 7 by CAN (registered trademark) communication or the like is a signal requesting the reading of the specific DTC or a signal requesting the reading of the regulation DTC.

It should be noted that, for example, a signal for requesting the reading of the specific DTC by hardware identification based on the connection state of the connectors 12 and 41 or software identification based on communication information (for example, a unique service ID) transmitted from the inspection tool 7 to the vehicle EUC5. It is possible to recognize whether the signal is a signal requesting reading of the regulation DTC.

In step 220, it is determined whether or not the signal related to the tool request is a DTC read request signal of the OBD regulation, that is, a signal requesting the read of the regulation DTC. If an affirmative judgment is made here, the routine proceeds to step 230, while if a negative judgment is made, the routine proceeds to step 240.

In step 230, since the read request of the regulation DTC is made, the DTC detected by the OBD regulation threshold is responded. That is, the regulation DTC is transmitted to the vehicle ECU 5, and the present processing is temporarily terminated.

On the other hand, in step 240, it is judged that the read request for the specific DTC is made, and the DTC detected by the security reference threshold is responded. That is, the specific DTC is transmitted to the vehicle ECU 5, and this processing is once terminated.

[1-4. effect]
The following effects can be obtained in the first embodiment.
(1a) In the first embodiment, a part of the regulation DTC is adopted as the specific DTC. Moreover, the 1st diagnostic part 27 which diagnoses the abnormality of the vehicle 3 based on the 1st diagnostic rule (for example, OBD regulation threshold value) is provided. Then, when the first diagnostic unit 27 detects an abnormality of a specific configuration (that is, an inspection target) such as a sensor or an actuator, a first failure code (that is, the regulation DTC) indicating an abnormality corresponding to the regulation DTC. ) Is remembered.

Further, a second diagnosis unit 29 for diagnosing the abnormality of the vehicle 3 is provided based on a second diagnosis rule (for example, a safety reference threshold value) different from the first diagnosis rule. Then, when the second diagnostic unit 29 detects the same abnormality of the inspection target, the second failure code (that is, the specific DTC) indicating the abnormality defined by the safety standard of the vehicle inspection is stored.

In other words, the vehicle storage unit 23 stores the results of diagnosis performed on the same inspection target using different thresholds (that is, the first failure code and the second failure code), and therefore, as necessary. By reading the first failure code and/or the second failure code from the vehicle storage unit 23, it is possible to obtain the failure code according to the required diagnostic level.

Therefore, at the time of vehicle inspection, only the specific DTC used for vehicle inspection can be acquired from the vehicle ECU 5. Therefore, since the state of the vehicle 3 can be surely determined by this specific DTC, it is possible to reliably determine whether the vehicle inspection has passed or failed.

(1b) In the first embodiment, an identifier is assigned to each DTC in order to identify the specific DTC and the regulation DTC. Therefore, since the specific DTC or the regulation DTC stored in the vehicle storage unit 23 can be identified by the identifier, the inspection tool 7 can reliably acquire the desired DTC.

[1-5. Correspondence of wording]
In the first embodiment, the vehicle 3 corresponds to the vehicle, the vehicle electronic control unit 5 corresponds to the vehicle electronic control unit, the inspection tool 7 corresponds to the inspection tool, the diagnostic system 13 corresponds to the diagnostic system, and the vehicle The storage unit 23 corresponds to the storage unit, the first diagnosis unit 27 corresponds to the first diagnosis unit, and the second diagnosis unit 29 corresponds to the second diagnosis unit.

[2. Second Embodiment]
The second embodiment is basically the same as the first embodiment, and therefore the differences will be mainly described below. Note that the other points are the same as those in the first embodiment. The same components as those in the first embodiment are designated by the same reference numerals.

In the second embodiment, the vehicle ECU 5 diagnoses an abnormality related to the specific DTC or the regulation DTC according to an instruction from the inspection tool 7.
<Process in vehicle ECU>
This process is a process performed when the inspection tool 7 requests the vehicle ECU 5 for an abnormality diagnosis and a DTC read request.

As shown in FIG. 10, the vehicle ECU 5 determines in step 300 whether or not there is a tool request. In other words, it is determined whether or not there is a request from the inspection tool 7 to the vehicle ECU 5 for the abnormality diagnosis for detecting the regulation DTC or for detecting the specific DTC, and for reading the DTC obtained by the abnormality diagnosis. judge. If an affirmative judgment is made here, the routine proceeds to step 310, while if a negative judgment is made, this processing is once terminated.

It should be noted that the operation unit 37 performs an operation, that is, a signal (that is, a control signal) input from the operation unit 37 to perform an abnormality diagnosis for detecting the regulation DTC or a specific DTC, and detect the abnormality. Further, it is possible to instruct whether to read the regulation DTC or the specific DTC.

In step 310, since there is a tool request, the reading method is recognized as in step 210 of the first embodiment.
In step 320, the determination threshold is switched based on the signal included in the tool request. That is, when the abnormality diagnosis regarding the specific DTC and the reading of the specific DTC are instructed, the threshold value defined by the security standard (that is, the security standard threshold value) is set as the threshold value of the abnormality determination. On the other hand, when the abnormality diagnosis related to the regulation DTC and the reading of the regulation DTC are instructed, the threshold (that is, the OBD regulation threshold) defined by the OBD regulation is set.

In the following step 330, abnormality diagnosis is performed using the determination threshold value set based on the signal included in the tool request, and the diagnosis result is stored in the vehicle storage unit 23.
That is, when the abnormality diagnosis for detecting the specific DTC is instructed, the threshold defined by the safety standard (that is, the security reference threshold) is set as the threshold for the abnormality determination. On the other hand, when the abnormality diagnosis for detecting the regulation DTC is instructed, the threshold value defined by the OBD regulation (that is, the OBD regulation threshold value) is set.

In the following step 340, a response of the abnormality diagnosis performed in the step 330 is performed. That is, as a diagnosis result of the abnormality diagnosis, the regulation DTC and the specification are transmitted to the inspection tool 7 in response to a request from the inspection tool 7, and the present processing is temporarily ended.

The second embodiment has the same effects as the first embodiment. Further, there is an advantage that abnormality diagnosis can be performed at a desired timing in response to a request from the inspection tool 7 and the diagnosis result can be transmitted to the inspection tool 7.

[3. 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 various modifications can be implemented.

(1) In the above-described embodiment, the threshold used for determining whether or not there is an abnormality is switched in the case of performing abnormality diagnosis regarding the specific DTC (that is, the second failure code) and the regulation DTC (that is, the first failure code). The abnormality diagnosis logic may be switched.

For example, the abnormality diagnosis method may be switched such that the abnormality diagnosis regarding the regulation DTC is performed when the engine of the vehicle is in the idle state, and the abnormality diagnosis regarding the specific DTC is performed when the vehicle is in the traveling state. The threshold value may be switched when the abnormality diagnosis logic is switched.

(2) When the failure code used for determining whether or not the safety standard defined by the Road Transport Vehicle Act is met is used as the second failure code, the Road Transport Vehicle Act is used as the first failure code. A fault code used for determining whether or not a standard defined by a different regulation (for example, J-OBDII) is satisfied may be used.

(3) In the above-described embodiment, the specific DTC and the regulation DTC are provided with the identifiers for distinguishing them. Good.

(4) In the above-described embodiment, the inspection tool is used to inspect the specific DTC or the regulation DTC. However, an application that can realize the same function as the inspection tool is stored in a communication terminal such as a smartphone or a personal computer. A communication terminal such as a smartphone, a personal computer, or the like may have the same function as the inspection tool of the above-described embodiment.

(5) Further, when a well-known VCI is connected to the port of the connector of the vehicle ECU, the inspection tool, the communication terminal such as the smartphone, the personal computer and the like are configured so as to communicate with the VCI. The same effect as can be obtained. Note that VCI is an abbreviation for Vehicle Communication Interface.

(6) A plurality of functions of one constituent element in the embodiment may be realized by a plurality of constituent elements, or one function of one constituent element may be realized by a plurality of constituent elements. .. Further, a plurality of functions of a plurality of constituent elements may be realized by one constituent element, or one function realized by a plurality of constituent elements may be realized by one constituent element. Further, a part of the configuration of the above embodiment may be omitted. Further, at least a part of the configuration of the above-described embodiment may be added or replaced with respect to the configuration of the other above-described embodiment.

(7) In addition to the electronic control devices described above, a system having the electronic control device as a component, a program for causing a computer to function as the electronic control device, and a non-transitional actual state of a semiconductor memory or the like in which the program is recorded The present disclosure can be implemented in various forms such as a recording medium and an electronic control method.

3: Vehicle, 5: Vehicle electronic control device, 7: Inspection tool, 13: Diagnostic system, 23: Vehicle storage unit, 27: First diagnostic unit, 29: Second diagnostic unit

Claims (8)

A vehicle electronic control unit (5) mounted on a vehicle (3), comprising:
A first diagnosis configured to diagnose an abnormality of the specific configuration of the vehicle based on a first diagnostic rule that defines the content of a diagnosis for detecting an abnormality related to the specific configuration of the vehicle. Part (27),
It is configured to diagnose an abnormality of the specific configuration based on a second diagnostic rule different from the first diagnostic rule that defines the content of the diagnosis for detecting the abnormality related to the specific configuration. A second diagnostic unit (29)
When the abnormality of the specific configuration is detected by the first diagnostic unit, the first failure code indicating the abnormality is stored, and the abnormality of the specific configuration is detected by the second diagnostic unit. Storage unit (23) configured to store the second failure code indicating the abnormality,
A vehicle electronic control device comprising: The vehicle electronic control device according to claim 1,
The first diagnostic rule and the second diagnostic rule are respectively an abnormality diagnosis logic for detecting an abnormality relating to the specific configuration, and/or a threshold used for determining whether or not there is an abnormality.
Vehicle electronic control unit. The vehicle electronic control device according to claim 1 or 2, wherein
The second failure code is a failure code used for determining whether or not the safety standard defined by the Road Transport Vehicle Law is met,
The first failure code is a failure code used to determine whether or not a standard defined by a law different from the Road Transport Vehicle Law is met.
Vehicle electronic control unit. The vehicle electronic control device according to any one of claims 1 to 3,
The first failure code and the second failure code are distinguished by a given identifier, and the areas in which the first failure code and the second failure code are stored are different. And a configuration distinguished by the fact that each code of the first failure code and the second failure code itself is different,
Vehicle electronic control unit. The vehicle electronic control device according to any one of claims 1 to 4,
In response to a request from the inspection tool, the first failure code and/or the second failure code stored in the storage unit is output.
Vehicle electronic control unit. The vehicle electronic control device according to any one of claims 1 to 5,
According to a request from the inspection tool, the first diagnosis unit and the second diagnosis unit are configured to perform diagnosis.
Vehicle electronic control unit. A vehicle electronic control device according to any one of claims 1 to 6,
An inspection tool which is connected to the vehicle electronic control unit and communicates with the vehicle electronic control unit,
Is equipped with
The vehicle electronic control unit includes a device-side connector, the inspection tool includes a tool-side connector,
Outputting the first failure code and/or the second failure code from the vehicle electronic control device side to the inspection tool side according to the connection state of the device side connector and the tool side connector. It is configured,
Diagnostic system. A vehicle electronic control device according to any one of claims 1 to 6,
An inspection tool for communicating with the vehicle electronic control unit,
Is equipped with
On the basis of a control signal transmitted from the inspection tool side to the vehicle electronic control unit side and instructing the output of the first failure code and/or the second failure code, The inspection tool side is configured to output the first failure code and/or the second failure code,
Diagnostic system.

Images