JP7211036B2 - Vehicle electronic controller and diagnostic system - Google Patents

Description

FIELD OF THE DISCLOSURE The present disclosure relates to vehicle electronic controllers on board a vehicle and diagnostic systems comprising vehicle electronic controllers and inspection tools.

2. Description of the Related Art Conventionally, OBD is known as a function of an in-vehicle electronic control device (that is, a vehicle electronic control device), for example, as described in Patent Document 1 below. OBD stands for On-board Diagnostics. This OBD detects the occurrence of an abnormality in various sensors, actuators, etc. mounted on the vehicle, and records a fault code corresponding to the abnormality. The fault code is hereinafter also referred to as DTC. DTC is an abbreviation for Diagnostic Trouble Code.

Moreover, in recent years, in order to detect an abnormality related to vehicle exhaust gas, various laws, regulations, etc. (that is, laws and regulations) stipulating OBD related to exhaust gas have been established both in Japan and abroad. According to this regulation (that is, OBD regulation), various DTCs that indicate an abnormality related to exhaust gas are set, and the abnormality diagnosis logic when diagnosing abnormality and the judgment value (that is, threshold value) at the time of abnormality diagnosis. is set.

JP-A-5-172706

The DTC described above indicates an abnormality in the past related to vehicle exhaust gas or the like. Therefore, in the future, for example, in the automobile inspection and registration system (that is, car inspection), it is conceivable that this DTC will be used for inspecting the state of vehicles, but it is necessary to fully examine it.

Therefore, when the DTC is used for vehicle inspection as described below, the inventors of the present application have found the following problems.
For example, among the DTCs, a predetermined DTC that indicates a defect that does not meet the safety standards of the Road Trucking Vehicle Law is defined as a specific DTC, and when this specific DTC is read by an inspection tool (i.e., a scan tool), it fails the vehicle inspection. can be considered. In other words, if the specific DTC is stored in the vehicle electronic control unit, it is conceivable that the vehicle inspection will be rejected.

In this way, when DTCs are used for vehicle inspections, it is conceivable to adopt, for example, DTCs set by OBD regulations as specific DTCs used for vehicle inspections. Note that, hereinafter, the DTC set by the OBD regulation may be referred to as the regulation DTC.

By the way, the legal DTC and the specific DTC are originally DTCs stipulated by separate legal regulations. Therefore, in the future, if a higher standard (that is, a stricter standard) than the legal OBD standard is required as the standard for the specific DTC, Coordination between legal DTCs and specific DTCs is considered necessary.

For example, as shown in FIG. 2A, when considering the output voltage of a predetermined sensor, the standard for judging abnormality of the legal DTC (for example, the OBD legal threshold) is higher than the standard for judging abnormality of the specific DTC (for example, the safety standard threshold). When it is low, that is, when the OBD regulation threshold is a stricter value than the safety standard threshold, it seems that there is no problem even if the regulation DTC is adopted as the specific DTC. Here, it is determined that the output voltage is higher than the threshold as abnormal.

However, for example, as shown in FIG. 2B, when the OBD regulation threshold is higher than the safety standard threshold, that is, when the OBD regulation threshold is less strict than the safety standard threshold, adopting the regulation DTC as the specific DTC causes a problem. It seems that there is. In other words, in the case of vehicle inspection, it is necessary to determine that there is an abnormality when the output voltage reaches the safety standard threshold. There is a risk that it will be determined that there is no abnormality.

One aspect of the present disclosure is to provide a vehicle electronic control device and a diagnostic system that can appropriately perform vehicle inspections using DTC.

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

The second diagnostic unit is configured to follow a second diagnostic rule different from the first diagnostic rule, which defines diagnostic content for detecting an abnormality related to the specific configuration (i.e., diagnosis target of the first diagnostic unit). Diagnosis of specific configuration anomalies based on

The storage unit stores a first failure code indicating the abnormality when the first diagnosis unit detects a specific configuration abnormality, and stores the first failure code indicating the abnormality, and when the second diagnosis unit detects the specific configuration abnormality. If so, it stores a second fault code indicating an abnormality.

According to such a configuration, when the first diagnostic unit detects an abnormality in the specific configuration, the first failure code indicating the abnormality is stored, and the second diagnostic unit detects the specific configuration. When an abnormality is detected, the second trouble code indicating the trouble is stored, so that it is possible to take measures according to each trouble code.

That is, the storage unit stores the first failure code and the first failure code based on the results of diagnosing the same diagnosis target based on different diagnostic rules (for example, different abnormality diagnosis logic and different thresholds used for abnormality determination). A second fault code is stored. Therefore, since the first failure code and/or the second failure code can be read out from the storage unit as required, the failure code corresponding to the requested content of the diagnosis result (for example, diagnosis level) can be obtained. .

That is, since it is possible to acquire a diagnosis result corresponding to the content of the request, it is possible to take appropriate measures such as performing repairs or judging the pass/fail of vehicle inspection according to the diagnosis result.
For example, by selecting and acquiring a specific DTC from the vehicle electronic control unit using an inspection tool, it is possible to reliably determine the state of the vehicle. becomes possible.

b) Another aspect of the present disclosure is a diagnostic system (13) comprising a vehicle electronic controller and an inspection tool.
The diagnostic system comprises the vehicle electronic controller described above and a test tool (7) connected to and in communication with the vehicle electronic controller. Further, the vehicle electronic control unit has a device side connector (25) and the inspection tool has a tool side connector (41).

This diagnostic system transmits a first fault code and/or a fault code from the vehicle electronic control device side to the inspection tool side according to the connection state (for example, indirect or direct connection state) between the device-side connector and the tool-side connector. Alternatively, it is configured to output a second fault code.

According to such a configuration, the same effect as that of one aspect of the present disclosure described above can be obtained.
c) Yet another aspect of the present disclosure is a diagnostic system (13) comprising a vehicle electronic controller and an inspection tool.

The diagnostic system includes the vehicle electronic controller described above and an inspection tool connected to the vehicle electronic controller and communicating with the vehicle electronic controller.
Then, the diagnostic system operates on the vehicle electronic control device side based on a control signal instructing output of the first fault code and/or the second fault code, which is transmitted from the inspection tool side to the vehicle electronic control device side. is configured to output the first fault code and/or the second fault code from to the inspection tool side.

According to such a configuration, the same effect as that of one aspect of the present disclosure described above can be obtained.
It should be noted that the symbols in parentheses described in this column and the scope of claims indicate the correspondence with specific means described in the embodiment described later as one mode, and the technical scope of the present disclosure is It is not limited.

1 is a block diagram showing a vehicle inspection system according to a first embodiment; FIG. Explanatory drawing which shows the relationship between a security standard threshold value and an OBD regulation threshold value. FIG. 4 is an explanatory diagram showing the relationship between legal DTCs and specific DTCs; 1 is a block diagram showing a vehicle electronic control device according to a first embodiment; FIG. FIG. 4 is an explanatory diagram showing identifiers of a first failure code and a second failure code; FIG. 2 is a block diagram showing the inspection tool of the first embodiment; FIG. FIG. 2 is a sequence diagram showing a communication procedure between the vehicle electronic control device and the inspection tool according to the first embodiment; 4 is a flowchart showing processing (1) of the vehicle electronic control device of the first embodiment; 4 is a flowchart showing processing (2) of the vehicle electronic control device of the first embodiment; 9 is a flowchart showing processing of the vehicle electronic control device of the second embodiment;

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

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

Although an example in which the vehicle ECU 5 and the inspection tool 7 are connected via a cable 11 is given here, they may be connected wirelessly. In addition, the diagnostic system 13 has a configuration including a vehicle ECU 5 and an inspection tool 7 .

In the vehicle inspection system 1 described above, processing for vehicle inspection and the like are performed as follows.
First, among the DTCs, which are failure codes indicating abnormalities in the vehicle 3, predetermined DTCs indicating failures that do not meet the safety standards of the Road Transport Vehicle Law are defined as specific DTCs. Note that the specific DTC corresponds to, for example, the second fault code.

When an abnormality corresponding to a 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 from the vehicle ECU 5 by the inspection tool 7 during vehicle inspection, the vehicle inspection is rejected.

That is, if a DTC for which safety standards are established is set as a 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, the specific DTC information, which is information about 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 whether the specific DTC has occurred in the vehicle 3. .

In addition to the above-described specific DTC, there is an OBD regulation (for example, J-OBDII), which is a regulation of laws related to exhaust gas, for example, in order to detect an abnormality related to exhaust gas. The DTC set in (that is, the legal DTC) is also stored in the vehicle ECU 5 . Note that the legal DTC corresponds to, for example, the first fault code.

Therefore, it is possible to diagnose the state of the vehicle 3 by reading the legal DTC from the vehicle ECU 5 in addition to the specific DTC.
For example, as shown in FIG. 2A, when considering the output voltage of a predetermined sensor, the standard for judging abnormality of legal DTC (for example, OBD legal threshold) is lower than the standard for judging abnormality of specific DTC (for example, safety standard threshold). A case (that is, a case where the criterion is strict) is conceivable. In this case, even if the legal DTC is adopted as the specific DTC, it seems that there is no problem. Here, it is determined that the output voltage is higher than the threshold as abnormal.

On the other hand, for example, as shown in FIG. 2B, it is conceivable that the OBD regulation threshold is higher than the safety standard threshold. , based on the safety standard threshold value, diagnose the abnormality.

In the first embodiment, as shown in FIG. 3, among many DTCs, predetermined DTCs indicating, for example, an abnormality related to exhaust gas are set as legal DTCs, and predetermined DTCs among the legal DTCs are designated as specific DTCs. is set.

[1-2. Each configuration]
Next, each configuration 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 device centered on a microcomputer that constitutes the vehicle arithmetic processing unit 21. When the vehicle is running or the like, an abnormality occurs in various on-vehicle sensors, actuators, or the like. It has an OBD function to detect that.

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

The vehicle arithmetic processing unit 21 has a first diagnostic unit 27 and a second diagnostic unit 31 as functional components realized by the CPU executing a program.
The first diagnosing unit 27 diagnoses an abnormality of a specific configuration, which is an abnormality detection target, based on a first diagnostic rule that defines the content of diagnosis. Note that the specific configuration is an object (inspection object) whose abnormality is to be detected, such as various on-vehicle sensors and actuators.

The second diagnostic unit 29 performs the same inspection based on a second diagnostic rule (e.g., a threshold value) different from the first diagnostic rule, which defines the content of diagnosis for the inspection target of the first diagnostic unit 27. Diagnose the abnormality of the target.

For example, if the test target of the first diagnostic unit 27 includes a certain sensor (eg, oxygen sensor), the test target of the second diagnostic unit 29 also includes the same sensor (eg, oxygen sensor). Although the first diagnosis section 27 and the second diagnosis section 29 diagnose the same object to be examined, they can also diagnose other objects to be examined.

Here, the first diagnostic rule and the second diagnostic rule are, respectively, an abnormality diagnosis logic for detecting an abnormality in an object to be inspected and/or a threshold value used for determining whether or not there is an abnormality. A threshold will be described as an example.

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

Here, the second trouble code is a trouble code used for judging whether or not the vehicle complies with safety standards stipulated by the Road Transport Vehicle Act (i.e., judging pass/fail of vehicle inspection), that is, a trouble code corresponding to a specific DTC. be. On the other hand, the first failure code is a failure code used to determine whether or not the standard defined by regulations (eg, J-OBD II) different from the Road Trucking Vehicle Act is met, that is, a failure code corresponding to the DTC regulation. is.

The first failure code (regulatory DTC) and the second failure code (specific DTC) are distinguished by assigned identifiers.
For example, as shown in FIG. 5, for example, when "P1234" is defined as a DTC indicating an abnormality in a certain sensor, even if the first diagnosis unit 27 detects an abnormality, 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 (ie, legal DTC) and the second failure code (ie, specific DTC), the minimum unit of data when transmitting/receiving and storing data is , is assigned an identifier. For example, as shown in FIG. 5(a), the minimum unit of data including DTC is given an identifier of "01" indicating that the DTC is a legal DTC immediately after the DTC "P1234". ing. Also, as shown in FIG. 5(b), the minimum unit of data including DTC is given an identifier of "02" indicating that the DTC is a specific DTC.

Therefore, the identifier immediately following the fault code makes it possible to distinguish whether the fault code is a primary fault code (ie legal DTC) or a secondary fault code (ie specific DTC).
As a method for distinguishing between the first failure code and the second failure code, other than the method using the identifier, for example, a first storage area for storing only the first failure code and a second failure code and a method of setting a second storage area for storing only. In this case, a desired type of failure code can be obtained by searching the storage area corresponding to the desired failure code.

Alternatively, for example, instead of assigning an identifier as described above, the first failure code and the second failure code may be distinguished by using different codes for the first failure code and the second failure code. may be separated.

<Inspection tool>
As shown in FIG. 6, the inspection tool 7 has a display 33 for displaying various displays, a tool electronic control unit (that is, a tool ECU) 35 for controlling the operation of the inspection tool 7, and can be manually operated by an operator. an operation unit 37, a tool communication unit 39 for communicating with the management server 9, and a 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 section 43 that performs various calculations, and a tool storage section 45 that stores various data.
The tool arithmetic processing unit 43 is composed of a CPU, a ROM, a RAM, etc., although not shown. For example, the tool calculation processing unit 43 requests the management server 9 to transmit specific DTC information, requests the vehicle ECU 5 to transmit specific DTCs or legal DTCs, and obtains the information. control.

The tool storage unit 45 is a rewritable non-volatile memory such as a flash memory, and is configured to store specific TDC information and the like acquired from the management server 9 . Moreover, it is configured to store specific DTCs and regulatory DTCs acquired from the vehicle ECU 5 .

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 normally not connected to the management server 9, but is connected to the management server 9 when necessary by the operator's operation, and downloads the latest specific DTC information, for example.

In other words, the inspection tool 7 is of a stand-alone type, and is used off-line rather than always on-line while being connected to the management server 9 . The inspection tool 7 may be connected to the management server 9 always online.

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

Further, the method of realizing each process executed by the vehicle ECU 5 and the tool ECU 35 is not limited to software, and a part or all of the functions may be realized using one or more pieces of hardware. For example, when the above functions are realized by an electronic circuit that is hardware, the electronic circuit may be realized by a digital circuit including many 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, during vehicle inspection, the inspection tool 7 requests the vehicle ECU 5 to read (A) specific DTCs and/or regulatory DTCs.

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

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

Next, the process performed by vehicle ECU5 is demonstrated concretely.
<Process (1) in vehicle ECU>
This process (1) is a process normally performed in vehicle ECU5.

In the vehicle ECU 5, as shown in FIG. 8, at step 100, it is determined whether or not it is time to perform abnormality diagnosis (that is, diagnosis start timing) by means of OBD in the vehicle. If an affirmative determination is made here, the process proceeds to step 110, and if a negative determination is made, this process is temporarily terminated.

As the diagnosis start timing, a conventional diagnosis start timing set for detecting each DTC, such as every predetermined period, can be used.
At step 110, diagnostics are performed according to OBD regulatory thresholds. That is, the abnormality diagnosis corresponding to the legal DTC is performed using the standard for judging the abnormality of the legal DTC (for example, the OBD legal threshold). In other words, an inspection is performed to detect an abnormality that corresponds to the legal DTC.

In the subsequent step 120, it is determined whether or not an abnormality corresponding to a legal DTC has been detected as a result of the diagnosis based on the OBD legal threshold. If the determination is affirmative here, the process proceeds to step 130 , and if the determination is negative, the process proceeds to step 140 .

In step 130, since an abnormality corresponding to the legal DTC was detected in step 120, the DTC is stored according to the OBD regulation. That is, the vehicle storage unit 23 stores a first failure code (that is, a legal DTC) indicating that an abnormality corresponding to the legal DTC has been detected. When storing the first failure code, a predetermined identifier is also stored to indicate that it is the first failure code. Then proceed to step 140 .

On the other hand, in step 140, since no abnormality corresponding to the legal DTC was detected in step 120, a diagnosis is made based on the safety standard threshold value. That is, the abnormality diagnosis corresponding to the specific DTC is performed using the abnormality determination standard (for example, safety standard threshold value) of the specific DTC. In other words, an inspection is performed to detect an abnormality corresponding to the specific DTC.

In the subsequent step 150, it is determined whether or not an abnormality corresponding to the specific DTC has been detected as a result of the diagnosis based on the safety standard threshold value. If an affirmative determination is made here, the process proceeds to step 160, and if a negative determination is made, this process is temporarily terminated.

At step 160, since an abnormality corresponding to the specific DTC was detected at step 150, the DTC is stored according to safety standards. In other words, the second fault code (that is, the specific DTC) indicating that an abnormality corresponding to the specific DTC has been detected is stored in the vehicle storage unit 23, and this process is terminated once. When storing the second failure code, 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 that is executed when the inspection tool 7 requests the vehicle ECU 5 to read the DTC.

In the vehicle ECU 5, as shown in FIG. 9, at step 200, it is determined whether or not there is a tool request. That is, it is determined whether or not there is a DTC reading request from the inspection tool 7 to the vehicle ECU 5 . If an affirmative determination is made here, the process proceeds to step 210, and if a negative determination is made, this process is temporarily terminated.

By operating the operation unit 37, that is, by a signal (that is, a control signal) input from the operation unit 37, it is possible to instruct whether to read the specific DTC or the legal DTC.

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

For example, hardware identification based on the connection state of the connectors 12 and 41, etc., and software identification based on communication information (for example, unique service ID, etc.) transmitted from the inspection tool 7 to the vehicle EUC 5 may determine whether the signal requesting reading of the specific DTC is , a signal requesting reading of a legal DTC can be recognized.

In step 220, it is determined whether or not the signal regarding the tool request is a signal for a DTC reading request of the OBD regulations, ie, a signal requesting reading of the regulation DTC. If the determination is affirmative, the process proceeds to step 230, and if the determination is negative, the process proceeds to step 240.

In step 230, a request to read regulatory DTCs has been made, so DTCs detected by OBD regulatory thresholds are responded to. That is, the legal DTC is transmitted to the vehicle ECU 5, and this process is terminated once.

On the other hand, in step 240, it is determined that a specific DTC read request has been made, and a DTC detected according to the safety standard threshold value is responded. That is, the specific DTC is transmitted to the vehicle ECU 5, and this process is once terminated.

[1-4. effect]
The following effects can be obtained in the first embodiment.
(1a) In the first embodiment, part of legal DTCs is adopted as specific DTCs. It also includes a first diagnosis unit 27 that diagnoses an abnormality of the vehicle 3 based on a first diagnosis rule (for example, OBD legal threshold). When the first diagnostic unit 27 detects an abnormality in a specific configuration (that is, an object to be inspected) such as a sensor or actuator, a first failure code (that is, a legal DTC) indicating an abnormality corresponding to the legal DTC ).

Furthermore, a second diagnosis section 29 is provided for diagnosing an abnormality of the vehicle 3 based on a second diagnosis rule (for example, safety standard threshold value) different from the first diagnosis rule. When the second diagnostic unit 29 detects an abnormality of the same object to be inspected, it stores a second failure code (that is, a specific DTC) indicating an abnormality specified by safety standards for vehicle inspection.

That is, the vehicle storage unit 23 stores the results of diagnosing the same inspection object using different thresholds (that is, the first failure code and the second failure code). By reading out the first trouble code and/or the second trouble code from the vehicle storage unit 23, it is possible to obtain the trouble code corresponding to the required level of diagnosis.

Therefore, at the time of vehicle inspection, only the specific DTC used for vehicle inspection can be obtained from the vehicle ECU 5 . Therefore, it is possible to reliably determine the state of the vehicle 3 based on this specific DTC, so that it is possible to reliably determine whether the vehicle inspection has passed or failed.

(1b) In the first embodiment, an identifier is given to each DTC in order to distinguish between a specific DTC and a regulatory DTC. Therefore, since the identifier can identify the specific DTCs and legal DTCs stored in the vehicle storage unit 23, the inspection tool 7 can reliably acquire the desired DTCs.

[1-5. Correspondence of wording]
In the first embodiment, the vehicle 3 corresponds to the vehicle, the vehicle electronic control device 5 corresponds to the vehicle electronic control device, 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]
Since the second embodiment is basically the same as the first embodiment, differences will be mainly described below. In addition, it is the same as that of 1st Embodiment except difference. Moreover, the same code|symbol is attached|subjected to the structure similar to 1st Embodiment.

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

In the vehicle ECU 5, as shown in FIG. 10, at step 300, it is determined whether or not there is a tool request. That is, the inspection tool 7 performs an abnormality diagnosis for detecting legal DTCs or specific DTCs for the vehicle ECU 5, and determines whether or not there is a request to read out the DTCs obtained thereby. judge. If an affirmative determination is made here, the process proceeds to step 310, and if a negative determination is made, this process is temporarily terminated.

By operating the operation unit 37, that is, by a signal (that is, a control signal) input from the operation unit 37, an abnormality diagnosis for detecting a legal DTC or a specific DTC is performed. In addition, it is possible to instruct whether to read legal DTCs or specific DTCs.

At step 310, since there is a tool request, the reading method is recognized as in step 210 of the first embodiment.
At step 320, the decision threshold is switched based on the signal contained in the tool request. That is, when an abnormality diagnosis and reading of the specific DTC are instructed, a threshold defined by the safety standard (that is, the safety standard threshold) is set as the threshold for abnormality determination. On the other hand, when the abnormality diagnosis related to the legal DTC and the readout of the legal DTC are instructed, the threshold defined by the OBD regulation (that is, the OBD regulation threshold) is set.

In subsequent step 330 , an abnormality diagnosis is performed using a 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 an abnormality diagnosis for detecting a specific DTC is instructed, a threshold defined by safety standards (that is, a safety standard threshold) is set as a threshold for abnormality determination. On the other hand, when an abnormality diagnosis for detecting a regulatory DTC is instructed, a prescribed threshold defined by the OBD regulation (that is, the OBD regulation threshold) is set.

At subsequent step 340, a response to the abnormality diagnosis performed at step 330 is performed. That is, as the diagnosis result of the abnormality diagnosis, the regulation DTC and identification are sent to the inspection tool 7 in response to the request from the inspection tool 7, and this process is terminated once.

The second embodiment has the same effect as the first embodiment. In addition, there is an advantage that an 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 made.

(1) In the above-described embodiment, the threshold used for determining whether or not there is an abnormality is switched when performing an abnormality diagnosis for a specific DTC (ie, the second failure code) and a legal DTC (ie, the first failure code). , the abnormality diagnosis logic may be switched.

For example, the method of abnormality diagnosis may be switched such that the abnormality diagnosis regarding the legal DTC is performed when the engine of the vehicle is idling, and the abnormality diagnosis regarding the specific DTC is performed when the vehicle is running. When switching the abnormality diagnosis logic, the threshold may be switched.

(2) When the second failure code is a failure code used to determine whether or not the safety standards stipulated by the Road Transport Vehicle Act are met, the first failure code is the Road Transport Vehicle Act. A fault code that is used to determine whether or not a standard defined by a different regulation (eg, J-OBDII) is met may be used.

(3) In the above embodiment, identifiers are assigned to specific DTCs and legal DTCs to distinguish them. good.

(4) In the above-described embodiment, the inspection tool was used to inspect the specific DTC and legal DTC. , a communication terminal such as a smartphone, a personal computer, or the like may be provided with the same function as the inspection tool of the above-described embodiment.

(5) In addition, when connecting a well-known VCI to the port of the connector of the vehicle ECU, by configuring an inspection tool, a communication terminal such as a smartphone, a personal computer, etc., so as to communicate with the VCI, You can get the same effect as Note that VCI is an abbreviation for Vehicle Communication Interface.

(6) A plurality of functions possessed by one component in the above embodiment may be realized by a plurality of components, or a function possessed by one component may be realized by a plurality of components. . Also, a plurality of functions possessed by a plurality of components may be realized by a single component, or a function realized by a plurality of components may be realized by a single component. Also, part of the configuration of the above embodiment may be omitted. Moreover, at least part of the configuration of the above embodiment may be added or replaced with respect to the configuration of the other above embodiment.

(7) In addition to each electronic control device described above, non-transitional realities such as a system having the electronic control device as a component, a program for making a computer function as the electronic control device, a semiconductor memory recording this program, etc. The present disclosure can also be implemented in various forms such as recording media and electronic control methods.

3: vehicle, 5: vehicle electronic controller, 7: inspection tool, 13: diagnostic system, 23: vehicle storage unit, 27: first diagnostic unit, 29: second diagnostic unit

Claims (6)

A vehicle electronic control device (5) mounted on a vehicle (3),
Diagnosing the abnormality of the specific configuration of the vehicle based on a first diagnosis rule that defines details of diagnosis for detecting an abnormality related to the specific configuration of the vehicle, and if the abnormality is detected, a first diagnostic unit (27) configured to determine that the anomaly according to one diagnostic rule is detected;
Diagnosing the abnormality of the specific configuration based on a second diagnosis rule different from the first diagnosis rule, which defines the content of the diagnosis for detecting the abnormality related to the specific configuration, a second diagnostic unit (29) configured to determine that the abnormality is detected according to the second diagnostic rule when the abnormality is detected;
When the abnormality of the specific configuration is detected by the first diagnosis unit, a first failure code indicating that the abnormality has been detected and confirmed is stored, and the second diagnosis unit stores the abnormality. A storage unit (23 )When,
with
Diagnosis by the first diagnosis unit and diagnosis by the second diagnosis unit can be switched according to a request from the inspection tool,
Vehicle electronic controller. The vehicle electronic control device according to claim 1,
The first diagnostic rule and the second diagnostic rule are, respectively, abnormality diagnosis logic for detecting the abnormality related to the specific configuration and/or a threshold value used to determine whether the abnormality exists. ,
Vehicle electronic controller. The vehicle electronic control device according to claim 1 or 2,
The second failure code is a failure code used to determine whether or not the safety standards stipulated by the Road Trucking Vehicle Law are met,
The first failure code is a failure code used to determine whether or not the vehicle conforms to standards stipulated by regulations different from the Road Trucking Vehicle Law.
Vehicle electronic controller. 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 in which each code of the first failure code and the second failure code is different.
Vehicle electronic controller. A vehicle electronic control device according to any one of claims 1 to 4 ;
an inspection tool connected to the vehicle electronic control device and communicating with the vehicle electronic control device;
and
The vehicle electronic control device has a device-side connector, and the inspection tool has a tool-side connector,
According to the connection state between the device-side connector and the tool-side connector, the vehicle electronic control device side outputs the first fault code and/or the second fault code to the inspection tool side. It is configured,
diagnostic system. A vehicle electronic control device according to any one of claims 1 to 4 ;
an inspection tool that communicates with the vehicle electronic control device;
and
Based on a control signal instructing output of the first fault code and/or the second fault code, which is transmitted from the inspection tool side to the vehicle electronic control device side, the vehicle electronic control device side configured to output the first fault code and/or the second fault code to the inspection tool side,
diagnostic system.

Images