JP4265071B2 - Vehicle control apparatus and recording medium having self-diagnosis function - Google Patents

Description

[0001]
BACKGROUND OF THE INVENTION
The present invention relates to a self-diagnosis function of a vehicle control device that controls a vehicle, and further relates to a technique for realizing the self-diagnosis function by object-oriented programming.
[0002]
[Prior art]
In recent years, mechatronics technology, which combines mechanical technology and electronic technology, has made remarkable progress against the backdrop of advances in electronics technology such as the advent of high-performance microprocessors. As part of the progress of mechatronics, many computer systems have been adopted in vehicles such as automobiles. Such in-vehicle computer systems pursue resource saving, energy saving, driving performance, safety, comfort, etc., such as engine / drive system, driving / safety system, entertainment system, and other in-vehicle systems. It is installed everywhere.
[0003]
Among them, a computer system for vehicle control that requires particularly high reliability may cause a trouble in traveling unless the abnormality detection of each part in the system is accurately performed. Sometimes. Therefore, reliability is improved by providing the computer system with a self-diagnosis function. In other words, the operating state of the computer unit and sensors is automatically checked at an appropriate cycle, and when a failure occurs, a warning lamp (MIL) is turned on to notify the user of the failure, or the details of the failure are repaired by a person in charge of repair. As shown in FIG. 5, a diagnosis (hereinafter referred to as “diagnosis”) processing for storing an abnormal code (DTC) is enabled. The target of this diagnosis process includes about 200 sensors such as a crank angle sensor, a cam angle sensor, and a water temperature sensor, and currently reaches about 200. Hereinafter, the object of the diagnosis process is referred to as “diag object”.
[0004]
By the way, this diagnosis process does not simply determine the “normal” or “abnormal” by checking the operation state of the diagnosis target on a single occasion. This is because “normal” and “abnormal” also have levels. For example, when “abnormality” of the input signal system from the sensor is taken as an example, the temporary contact failure in the connector or the like is “abnormal”, and the complete disconnection is also “abnormal”. In the former case, a good operating state may be maintained thereafter, and in particular, the necessity for replacing parts may not be recognized. Therefore, even if it is determined that there is an abnormality once, for example, if no abnormality is detected for all diagnostic targets during the 40 warm-up cycle, all the abnormality codes stored so far are deleted. There was a control unit.
[0005]
[Problems to be solved by the invention]
The present invention focuses on the inconvenience caused by the abnormal codes stored therefor because there is a high possibility that the above-mentioned temporary abnormalities are detected during a limited period. This will be described.
[0006]
Examples of a period in which a temporary abnormality is likely to be detected include a vehicle assembly period in a factory and a travel period immediately after factory shipment. During the vehicle assembly period, the battery is temporarily fixed for operation confirmation, and therefore there is a high possibility that an abnormality in the battery connection will be detected. In addition, during the traveling period immediately after shipment from the factory, a small amount of metal scrap is generated from the operating part of the engine or the like, and therefore there is a high possibility that an abnormality will be detected due to the influence of the metal scrap. And both of these anomalies are temporary and not essential. However, in the conventional configuration, as described above, the erasure of the abnormal code is performed only when no abnormality is detected for 40 warm-up cycles for all diagnosis objects. Therefore, there is a problem that parts that are not originally required to be replaced are replaced based on the stored abnormal code, for example, when the user brings the vehicle to a repair shop or the like before the abnormal code is erased.
[0007]
In order to prevent this, it is conceivable that the abnormal code once stored is erased for each diagnosis target at a relatively early timing such as 20 warm-up cycles. However, since a plurality of abnormality detection methods may exist for a certain diagnosis target, it is not possible to simply delete the abnormality code stored for the diagnosis target. For example, when there are two methods A and B as an abnormality detection method for a diagnosis target, an abnormality code cannot be erased just because the abnormality detection by the method A is not performed. This is because there is a possibility that an abnormality is detected by the method B. Therefore, when a plurality of abnormality detection methods exist in the same diagnosis target, a configuration for deleting the abnormality code based on the plurality of abnormality detection results is required.
[0008]
And in adopting such a configuration, further consideration in the following points is necessary.
That is, the diagnosis target described above changes at the timing of the vehicle type, grade or model change. Therefore, it is desirable to adopt an object-oriented design that takes reusability into consideration. In other words, the processing that depends on the diagnosis target and the processing that does not depend on the diagnosis target are executed by another object, and the object that executes the processing that does not depend on the diagnosis target can be reused as it is. It can be used partially to create a new self-diagnosis program.
[0009]
The present invention makes it possible to erase abnormal information stored by temporary abnormality for each diagnosis target while ensuring reusability of the self-diagnosis program, and parts that do not need to be replaced are replaced. The purpose is to prevent this as much as possible.
[0010]
[Means for Solving the Problems and Effects of the Invention]
The vehicle control device according to claim 1, which has been made to achieve the above-described object, has a self-diagnosis function for storing abnormal time information corresponding to the diagnosis target based on the abnormality detection result of the diagnosis target. . Here, the abnormality time information includes at least an abnormality code indicating an abnormality content. In addition, the information at the time of abnormality is intended to include so-called freeze data indicating the vehicle state at the time of abnormality such as vehicle speed, engine speed, water temperature, throttle opening. In other words, the self-diagnostic function here is to store these abnormal-time information in, for example, a standby RAM or EEPROM based on the abnormality detection result, whereby the contents stored in the standby RAM or EEPROM are stored in a repair shop or the like. If it is read, the abnormal part can be specified.
[0011]
In the present invention, this self-diagnosis function is realized by executing a self-diagnosis program. And this self-diagnosis program Every Anomaly detection objects that execute processing and diagnostic targets Common It consists of a group of objects that execute processing. An anomaly detection object is prepared for each diagnosis target. Processing to detect anomalies ( Anomaly detection processing ) Execute. On the other hand, the object group executes a process of storing information at the time of abnormality based on the abnormality detection result by the abnormality detection object.
[0012]
Based on such a configuration, particularly in the present invention, when there are a plurality of methods for detecting an abnormality of the same diagnosis target, an abnormality detection object is prepared for each of the plurality of methods. And, at least one of these abnormality detection objects, when a predetermined condition is satisfied after abnormality detection is performed once, only when abnormality detection is not performed in another abnormality detection object related to the same diagnosis target, Instructs the invalid information to be invalidated. Here, when a predetermined condition is satisfied, for example, when no abnormality is detected during a predetermined number of warm-up cycles, for example, 20 warm-up cycles, or for example, 20 trips (period from turning on to off of the ignition key) It is conceivable that no abnormality is detected during a predetermined number of trips. Further, whether or not an abnormality is detected in another abnormality detection object is determined by referring to the global variable in a configuration in which the abnormality detection result of the abnormality detection object is substituted into a global variable, for example. In addition, when the abnormality detection result is, for example, internal information of the abnormality detection object, a message for reading the abnormality detection result is sent to the corresponding abnormality detection object, thereby making a determination with reference to the abnormality detection result. .
[0013]
When an abnormality detection object invalid instruction is issued from the abnormality detection object, the above-described object group invalidates the abnormality information. The reason for “invalidating” is not only to erase the stored abnormal information but also to mask the stored abnormal information. The masking process refers to, for example, setting a flag for abnormal time information so that the abnormal time information cannot be read. In this case, since the abnormal time information remains in the storage device itself, it cannot be read by a normal operation in a repair shop or the like, but the abnormal time information can be read and referred to by performing a special operation.
[0014]
According to the present invention, if the detected abnormality is temporary, the stored abnormality information is invalidated at a relatively early timing such as 20 warm-up cycles for each diagnosis target. As a result, it is possible to prevent parts that originally do not need to be replaced from being replaced.
[0015]
In addition, when at least one of a plurality of anomaly detection objects prepared for each anomaly detection method has not been anomaly detected by another anomaly detection object related to the same diagnosis target, the invalidity information invalid instruction is issued. I do. Therefore, just because an abnormality is not detected by a certain abnormality detection method, the abnormality code is not invalidated when an abnormality is detected by another method.
[0016]
Furthermore, it is the abnormality detection object that determines the abnormality detection result of the other abnormality detection object and sends an invalid instruction of the abnormality information to the object group. Accordingly, when the diagnosis target changes, only the abnormality detection object needs to be changed, and the object group need not be changed at all. Therefore, reusability of the self-diagnosis program can be ensured.
[0017]
Note that the abnormality detection object for instructing invalidity information invalidity detection should be performed with a method having a relatively high possibility of detecting an abnormality among abnormality detection objects related to the same diagnosis target. (Claim 2). For example, an abnormality detection object having the highest possibility of detecting an abnormality refers to an abnormality detection result of another abnormality detection object and issues an invalid instruction of information at the time of abnormality. However, the abnormality detection object that gives an invalid instruction is not limited to one as long as it has a relatively high possibility of detecting an abnormality.
[0018]
If an abnormality is not detected for an object with a relatively high possibility of detecting an abnormality, there is a low possibility that an abnormality will be detected for another object, and it is not necessary to perform judgment processing on all abnormality detection objects. It is. According to the present invention, since the determination process for determining whether or not the abnormality information is invalid is inserted into some (for example, one) abnormality detection objects, the processing program is simplified. Further, it is advantageous in that the number of executions of the determination process is reduced and the processing load is reduced.
[0019]
On the other hand, the object group can be configured as shown in claim 3, for example. That is, it is conceivable to include at least an abnormality confirmation object, an abnormality processing object, and an abnormality information storage object. At this time, each object operates as follows.
[0020]
The abnormality confirmation object determines whether or not it is a substantial abnormality based on the abnormality detection result by the abnormality detection object. For example, when the battery is disconnected, the abnormality may be detected even if the diagnosis target itself such as a sensor is normal due to the battery being disconnected. Further, when an abnormality determination is made by the abnormality confirmation object, the abnormality processing object makes a storage request for abnormality information. Then, the abnormal time information storage object stores the abnormal time information in accordance with the abnormal time information storage request by the abnormal time processing object.
[0021]
The determination as to whether or not the detected abnormality is substantial as described above, for example, the determination as to whether or not the abnormality is due to battery removal is a determination process common to each diagnosis. Therefore, by providing an abnormality confirmation object for executing this determination process, the entire program configuration is simplified, and further reusability can be achieved.
[0022]
Further, the configuration in which the abnormal time information storage object stores the abnormal time information in accordance with the request of the abnormal time processing object is as follows.
In the diagnosis process, not only the storage of information at the time of abnormality but also a warning lamp lighting / extinguishing process is generally performed to notify the user of the occurrence of the abnormality. In view of such a configuration, it is desirable to prepare an object that supervises abnormal-time processing such as storage of abnormal-time information and lighting / extinguishing of a warning lamp. This is because the program structure is easy to understand and expandability is enhanced. Therefore, in the present invention, an abnormality processing object is provided. In this way, for example, when the warning lamp is turned on / off, the abnormality processing object outputs a warning lamp turn-on / off request to the predetermined object, and the predetermined object turns on / off the warning light. It can be realized by doing.
[0023]
Assuming such a configuration, if there is an instruction to invalidate the abnormal time information from the abnormality detection object, the abnormal time processing object may make an invalid request for the abnormal time information. At this time, the abnormal time information storage object invalidates the abnormal time information in accordance with the invalid time information invalidation request from the abnormal time processing object.
[0024]
By the way, such a self-diagnosis program included in the vehicle control device is recorded on a computer-readable recording medium such as a floppy disk, a magneto-optical disk, a CD-ROM, or a hard disk, and is loaded into a computer system as necessary. It can be used by starting. In addition, a self-diagnosis program may be recorded as a computer-readable recording medium using a ROM or backup RAM, and the ROM or backup RAM may be incorporated into a computer system.
[0025]
DETAILED DESCRIPTION OF THE INVENTION
Hereinafter, an embodiment of the present invention will be described with reference to the drawings.
FIG. 1 is a configuration diagram showing the entire engine control system. This engine control system is mainly composed of an engine 11 and an engine control unit 16 that controls the engine 11. The engine control unit 16 corresponds to a “vehicle control device”.
[0026]
The engine 11 is supplied with intake air from an air cleaner through an intake pipe 12. The intake pipe 12 is provided with an air flow sensor 13 for measuring the intake air amount, an intake air temperature sensor 14 for detecting intake air temperature, and a throttle valve 15 driven by an accelerator pedal.
[0027]
Various signals indicating the state of the engine 11 are input to the engine control unit 16. If this signal is listed, the intake air amount detection signal from the air flow sensor 13, the opening degree detection signal of the throttle valve 15 from the throttle sensor 17, and the signal from the air-fuel ratio sensor 18 that detects the oxygen concentration contained in the exhaust gas. A battery voltage signal from the battery 19, a detection signal from the water temperature sensor 20, a rotation signal from the distributor 21 driven by the engine 11, and a cylinder discrimination signal.
[0028]
Further, the engine control unit 16 calculates a fuel injection amount corresponding to the operating state of the engine 11 based on these various detection signals, and for the injectors 22a to 22d set for each of the plurality of cylinders of the engine 11. A fuel injection command is output, and an ignition command signal is output to the igniter 23 to execute operation control of the engine 11.
[0029]
Furthermore, the engine control unit 16 also performs diagnosis of each part of the vehicle based on detection signals from each sensor group. For this reason, a test switch 24 for setting a diagnosis mode for outputting an abnormality detection result is arranged for the engine control unit 16, and a warning lamp 25 for displaying a diagnosis result as the test result. Is connected.
[0030]
The switch 26 is an ignition switch that connects the battery 19 to the engine control unit 16, and a starter switch 28 that controls the starter motor 27 in conjunction with the ignition switch 26 is provided.
Next, the engine control unit 16 will be described. FIG. 2 is a block diagram showing a configuration of the engine control unit 16 shown in FIG. The engine control unit 16 includes a CPU 31 that constitutes a computer system. Data from the analog input circuit 32 and the digital input circuit 33 are input to the CPU 31, and the analog input data from the analog input circuit 32 is converted into digital data by the A / D converter 34 and input to the CPU 31.
[0031]
The analog input circuit 32 receives the detection signal Us from the airflow sensor 13, the detection signal Thw from the water temperature sensor 20, the detection signal Tha from the intake air temperature sensor 14, and the voltage + B of the battery 19. On the other hand, in the digital input circuit 33, the cylinder discrimination signal G1 and the rotation angle signal Ne from the distributor 21, the lean / rich signal Ox corresponding to the oxygen concentration from the air-fuel ratio sensor 18, and the throttle valve 15 from the throttle sensor 17 are all provided. An idle signal Idle indicating that it is closed, a start signal STA from the starter switch 28, and a signal T for setting a diagnostic mode from the test switch 24 are input.
[0032]
The A / D converter 34 has a multiplexer function that sequentially selects and reads various detection signals input to the analog input circuit 32 in accordance with commands from the CPU 31 and converts them into digital data.
The power supply circuit 35 supplies the voltage + B of the battery 19 to the CPU 31 via the ignition switch 26 and also supplies the backup power supply Batt.
[0033]
Output data from the CPU 31 is supplied to output circuits 36, 37 and 38 and is taken out as an output signal from the engine control unit 16. That is, the output circuit 36 outputs an ignition command signal IGt to the igniter 23. Further, the output circuit 37 outputs a signal W representing the diagnosis result to control the lighting of the warning lamp 25. The output signal τq from the output circuit 38 indicates the fuel injection amount corresponding to the operating state of the engine 11, and is output to the injectors 22a to 22d to change the injection amount of these injectors 22a to 22d.
[0034]
Further, in the CPU (engine control unit) 31, a memory 39 for storing a self-diagnosis program described later is provided. The memory 39 is composed of a ROM and a standby RAM that retains data by being supplied with power even when the ignition switch 26 is turned off. The self-diagnosis program is stored in the ROM. As will be described later, an abnormal code is stored in the standby RAM by a self-diagnosis program.
[0035]
This embodiment is characterized by a self-diagnosis program stored in the ROM of the memory 39. Next, the self-diagnosis program will be described.
FIG. 3 is an explanatory diagram conceptually showing the structure (architecture) of the self-diagnosis program. The self-diagnosis program is composed of a plurality of programs designed in an object-oriented manner. As is already known, object-oriented design is based on the characteristics and behavior (operation) of an object modeled on a basic unit, compared to what conventional software focuses on processing (for example, fuel injection processing). Describes the process. This basic unit is referred to as an “object”, and an object-oriented designed program is described with this object as the minimum constituent unit. As a whole program, a series of processing is executed by connecting objects by exchanging requests and responses (hereinafter referred to as “messages”). The object includes data (attribute) and a method (procedure) for the data, and executes the method by a message from another object. In the present specification, the expression “object is ...” based on the object is used, but it is needless to say that it is actually realized by the CPU 31 executing the processing program. .
[0036]
FIG. 3 shows only the objects necessary for explaining the present embodiment. That is, the self-diagnosis program in this embodiment includes at least an abnormality detection object 100, an abnormality confirmation object 200, an abnormality processing object 300, and an abnormality code storage object 400.
[0037]
The abnormality detection object 100 detects an abnormality of a diagnosis target that is a target of self-diagnosis based on information such as each sensor group input to the engine control unit 16. This abnormality detection object 100 is prepared for each diagnosis target. For example, FIG. 3 shows a water temperature sensor abnormality detection object (hereinafter referred to as “water temperature sensor object”) 110 that detects an abnormality of the water temperature sensor 20 in the abnormality detection object 100, and an intake air temperature that detects an abnormality of the intake air temperature sensor 14. A sensor abnormality detection object (hereinafter referred to as “intake air temperature sensor object”) 120 and a throttle sensor abnormality detection object (hereinafter referred to as “throttle sensor object”) 130 for detecting abnormality of the throttle sensor 17 are shown. That is, here, the water temperature sensor 20, the intake air temperature sensor 14, and the throttle sensor 17 correspond to “diagnosis targets”.
[0038]
If there are a plurality of abnormality detection methods for the same diagnosis target, an abnormality detection object 100 is prepared for each of the plurality of abnormality detection methods. For example, if there are three abnormality detection methods for the water temperature sensor 20, three water temperature sensor objects 110a, 110b, and 110c are prepared as shown in FIG. Hereinafter, the three water temperature sensor objects 110a to 110c are described as an A water temperature sensor object 110a, a B water temperature sensor object 110b, and a C water temperature sensor object 110c.
[0039]
The abnormality confirmation object 200 determines whether the abnormality detected by each abnormality detection object 100 is a substantial abnormality. For example, when the battery 19 is disconnected, the abnormality may be detected even if the diagnosis target itself is normal due to the battery 19 being disconnected.
[0040]
The abnormal-time processing object 300 executes abnormal-time processing. The abnormal process includes a storage / mask request for an abnormal code and a request for turning on / off a warning lamp.
The abnormal code storage object 400 stores the abnormal code corresponding to the diagnosis target in the standby RAM of the memory 39. Alternatively, the abnormal code once stored in the memory 39 is masked. Masking means that an abnormal code stored in the standby RAM cannot be read out by normal operation by setting a flag corresponding to the abnormal code. In the present embodiment, only the abnormal code is stored / masked to avoid complication, but not only the abnormal code but also the vehicle speed, engine speed, water temperature, throttle at the time when the abnormality is determined. So-called freeze data indicating the vehicle state such as the opening degree may be stored / masked in the standby RAM.
[0041]
As described above, the objects 100 to 400 are combined by a message and execute a series of processes. Therefore, next, the connection of the objects 100 to 400 will be described with reference to a message sequence chart (hereinafter referred to as “MSC”).
[0042]
FIG. 4 is an MSC showing from abnormality detection of a diagnosis target to storage of an abnormality code. First, the abnormality detection object 100 executes an abnormality detection process (S1). When an abnormality to be diagnosed is detected in this abnormality detection process, an abnormality flag is set. Therefore, the abnormality detection object 100 issues a flag processing request to the abnormality confirmation object 200.
[0043]
When receiving the flag processing request, the abnormality confirmation object 200 executes the abnormality confirmation processing (S2). If it is determined in this abnormality confirmation process that there is a substantial abnormality, the abnormality confirmation object 200 sends an abnormality confirmation notification to the abnormality processing object 300.
[0044]
Then, the abnormal time processing object 300 executes the abnormal time processing (S3). In this abnormal process, an abnormal code storage request for the abnormal code storage object 400 is issued. In the process at the time of abnormality, a warning lamp lighting request is generally issued to another object (not shown), but since it is not necessary for the description of the embodiment, the warning lamp lighting request is omitted.
[0045]
When the abnormal code storage request is received, the abnormal code storage object 400 executes an abnormal code storage process (S4). As a result, the abnormal code corresponding to the diagnosis target determined to be abnormal is stored in the standby RAM of the memory 39.
Further, in this embodiment, if an abnormality to be diagnosed is not detected during 20 trips after the abnormality code is once stored, it is stored in the standby RAM of the memory 39 as a temporary abnormality. The abnormal code is masked for each diagnosis target.
[0046]
FIG. 5 is an MSC showing abnormal code mask processing. In the above-described abnormality detection process (S1), if no abnormality is detected during 20 trips after the abnormality is detected, a mask process request is issued to the abnormality processing object 300.
The abnormal time processing object 300 executes the abnormal time processing described above (S3), and issues an abnormal code mask request in accordance with the mask processing request. Thus, the abnormal code storage object 400 executes the abnormal code mask process (S5). As a result, the abnormal code stored in the standby RAM of the memory 39 corresponding to the diagnosis target is masked.
[0047]
However, as shown in FIG. 3, there are three water temperature sensor objects 110 a to 110 c of A to C as the abnormality detection object 100 for the water temperature sensor 20 to be diagnosed. Therefore, after the abnormality code corresponding to the water temperature sensor 20 is stored, for example, even when the A water temperature sensor object 110a does not detect an abnormality during the 20 trip, the B water temperature sensor object 110b detects the abnormality. Cases are also conceivable. Therefore, the A water temperature sensor object 110a needs to issue a mask processing request with reference to the abnormality detection results of the B and C water temperature sensor objects 110b and 110c.
[0048]
In this embodiment, the above-described mask processing request is devised on the premise that there are a plurality of abnormality detection objects 100 for the same diagnosis target.
Therefore, including this point, the details of the above-described abnormality detection process (S1), abnormality confirmation process (S2), abnormality code storage process (S4) and abnormality code mask process (S5) are based on the flowcharts of FIGS. explain. Note that the abnormality detection process (S1) will be described by taking the abnormality detection process in each of the three water temperature sensor objects 110a to 110c of A to C as an example. For the sake of explanation, the abnormality detection process executed by the A water temperature sensor object 110a is described as “A abnormality detection process”, and similarly, the abnormality detection process executed by the B water temperature sensor object 110b is called “B abnormality detection process”, C water temperature. The abnormality detection process executed by the sensor object 110c is described as “C abnormality detection process” to be distinguished. Each of the abnormality detection processes A to C detects an abnormality caused by the water temperature sensor 20 being out of range. Out-of-range refers to a situation where a signal is not output with a specified signal width. For example, the signal Thw that is supposed to be output in the range of 0 to 5V is always output at 2V or output in the range of 2 to 3V. Such a signal Thw having a certain value or within a certain range is referred to as “fixing of signal value”.
[0049]
6 and 7 are flowcharts showing the A abnormality detection process executed by the A water temperature sensor object 110a. The A abnormality detection process is to determine whether the signal value is stuck on the low temperature side, and performs abnormality detection based on a rise in water temperature due to warm-up.
First, in the first step (hereinafter, steps are simply indicated by symbol S) 1000, flag information is copied to a register. The flag information here includes an abnormality flag (normal: “0”, abnormality “1”) indicating an abnormality detection result and an abnormality determination flag (unconfirmed: “0”, confirmation “1”) indicating that the abnormality has been established. It is. These flags are prepared in the standby RAM of the memory 39 as global variables. In this process, the flag information determined in the previous process is saved as past flag information.
[0050]
In subsequent S1010, it is determined whether or not the engine is being started. If it is determined that the engine is being started (S1010: YES), an initialization process is executed in S1020, and then the process proceeds to S1110 in FIG. In the initialization process of S1020, the water temperature at engine startup is substituted for the startup water temperature Ts, the warm-up counter D is reset to “0”, and the trip flag Ft is set to “0”. On the other hand, if it is determined that the engine is not being started (S1010: NO), the process proceeds to S1030.
[0051]
In S1030, the warm-up counter D is incremented. In subsequent S1040, it is determined whether or not the water temperature T is lower than the feedback water temperature T (F / B). The feedback water temperature T (F / B) is a water temperature that is a condition for starting feedback control of the engine 11. If T <T (F / B) (S1040: YES), the process proceeds to S1050. On the other hand, when T ≧ T (F / B) (S1040: NO), the process proceeds to S1070.
[0052]
In S1050, it is determined whether or not the warm-up counter D is greater than the warm-up determination value Dth. This warm-up determination value Dth is used to determine whether or not the engine has been warmed up to such an extent that it is possible to shift to feedback control, and is calculated based on a starting water temperature Ts that is a water temperature when the engine is started. That is, when the starting water temperature Ts is relatively high, it is calculated to be small, and conversely, when the starting water temperature Ts is relatively low, it is calculated to be large. This is because if the water temperature Ts at the start is high, it takes time to warm up, and if it is low, it takes time to warm up. If D> Dth (S1050: YES), that is, if it is determined that the water temperature T is lower than the feedback water temperature T (F / B), the water temperature is indicated. Assuming that the signal value is fixed on the low temperature side, the abnormality flag FA is set to “1” in S1060, the normality determination counter S is reset to “0”, and the process proceeds to S1110 in FIG. On the other hand, when D ≦ Dth (S1050: NO), that is, when the warm-up is insufficient, the process of S1060 is not executed and the process proceeds to S1110 in FIG.
[0053]
In S1070, which is shifted when a negative determination is made in S1040, the abnormality flag FA is set to “0” as normal. In this case, the water temperature T is larger than the feedback water temperature T (F / B), and the signal value indicating the water temperature is not fixed to the low temperature side.
[0054]
In subsequent S1080, it is determined whether or not the trip flag Ft is “0”. The trip flag Ft is used to determine whether or not a negative determination has already been made in S1040 for each trip. If Ft = 0 (S1080: YES), the normality determination counter S is incremented (S1090), the trip flag Ft is set to “1” (S1100), and the process proceeds to S1110 in FIG. As a result, the normality determination counter S is incremented only once in each trip. On the other hand, if Ft ≠ 0 (S1080: NO), the processing of S1090 and S1100 is not executed, and the routine proceeds to S1110 in FIG.
[0055]
In S1110 in FIG. 7, a flag processing request is issued to the abnormality confirmed object 200. In subsequent S1120, it is determined whether or not the normality determination counter S is equal to or greater than “20”. If S ≧ 20 (S1120: YES), that is, if no abnormality is detected during 20 trips, the process proceeds to S1130. On the other hand, when S <20 (S1120: NO), the processing of S1130 and S1140 is not executed, and the present A abnormality detection processing is terminated.
[0056]
In S1130, it is determined whether or not the abnormality flags FB and FC are both “0”. The abnormality flags FB and FC are global variables that are set to “1” when an abnormality is detected in the B water temperature sensor object 110b and the C water temperature sensor object 110c, as will be described later. Therefore, the determination is made with reference to the global variables FB and FC here. Here, when FB = 0 and FC = 0 (S1130: YES), that is, when no abnormality is detected in both the water temperature sensor objects 110b and 110c of B and C, an abnormality processing object is obtained in S1140. A mask process request is issued to 300, and then the A abnormality detection process is terminated. On the other hand, when FB = 1 or FC = 1 (S1130: NO), that is, when an abnormality is detected in at least one of the water temperature sensor objects 110b and 110c of B or C, the process of S1140 is executed. Without completing the A abnormality detection process.
[0057]
Next, the B abnormality detection process executed by the B water temperature sensor object 110b will be described based on the flowchart of FIG. This B abnormality detection process detects abnormality based on the water temperature rise by acceleration operation.
First, in S2000, the flag information is copied to the register. In subsequent S2010, it is determined whether or not the engine is being started. If it is determined that the engine is being started (S2010: YES), an initialization process is executed in S2020, and then the process proceeds to S2100. In the initialization process of S2020, the minimum water temperature TL, the maximum water temperature TU, the minimum vehicle speed SL, and the maximum vehicle speed SU are initialized as the water temperature and vehicle speed at the time of starting the engine, respectively, and the idle OFF counter I is reset to “0”. Further, the water temperature at engine start is substituted for the water temperature Ts at start, and the acceleration mode counter MA is reset to “0”. On the other hand, if it is determined that the engine is not being started (S2010: NO), the process proceeds to S2030.
[0058]
In S2030, calculation target value update processing for updating a value to be calculated is executed. This calculation target value update processing is as shown in FIG. As shown in FIG. 9, when the process is started, the minimum vehicle speed SL and the maximum vehicle speed SU are updated. Specifically, if the minimum vehicle speed SL is larger than the current vehicle speed, the current vehicle speed is substituted for the minimum vehicle speed SL. If the maximum vehicle speed SU is smaller than the current vehicle speed, the current vehicle speed is substituted for the maximum vehicle speed SU. Subsequently, it is determined whether or not an idle state is set (S2210). The idle state means a state in which the throttle valve 15 in FIG. 1 is fully closed. Therefore, this determination is made based on the Idle signal from the throttle sensor 17. If it is determined that the engine is not in the idle state (S2210: NO), the idle OFF counter I is incremented (S2220), and the process proceeds to S2230. On the other hand, when it is determined that the vehicle is in the idle state (S2210: YES), the process of S2220 is not executed and the process proceeds to S2230. Furthermore, the minimum water temperature TL and the maximum water temperature TU are updated (S2230). Specifically, if the minimum water temperature TL is higher than the current water temperature, the current water temperature is substituted for the minimum water temperature TL. If the maximum water temperature TU is lower than the current water temperature, the current water temperature is substituted for the maximum water temperature TU.
[0059]
Returning to the flowchart of FIG. In S2040 following S2030, it is determined whether or not the difference (SU−SL) between the maximum vehicle speed SU and the minimum vehicle speed SL is equal to or greater than the acceleration determination value Ath. That is, it is determined whether or not a certain amount of acceleration operation has been performed. If (SU−SL) ≧ Ath (S2040: YES), the acceleration mode counter MA is incremented in S2050, and the current vehicle speed is substituted to reset the minimum vehicle speed SL and the maximum vehicle speed SU. Thereafter, the process proceeds to S2060. On the other hand, if (SU-SL) <Ath (S2040: NO), the process of S2050 is not executed and the process proceeds to S2060.
[0060]
In S2060, it is determined whether or not the difference (TU−TL) between the maximum water temperature TU and the minimum water temperature TL is equal to or greater than the water temperature deviation determination value Tth. Further, it is determined whether or not the starting water temperature Ts is equal to or lower than the water temperature determination value TH. That is, it is determined here whether or not there has been a certain increase in water temperature. However, when the water temperature Ts at the time of starting is low, the rate of increase in the water temperature is low, so that case is considered. Here, if (TU−TL) ≧ Tth or Ts ≦ TH (S2060: YES), it is determined to be normal, the abnormality flag FB is set to “0” (S2070), and the process proceeds to S2100. . On the other hand, if (TU-TL) <Tth and Ts> TH (S2060: NO), the process proceeds to S2080.
[0061]
In S2080, it is determined whether or not the acceleration mode counter MA is greater than or equal to a certain value Mth. Further, it is determined whether or not the idle OFF counter I is equal to or greater than a certain value Ith. The former is to determine whether or not a certain amount of acceleration operation has been performed a certain number of times. On the other hand, the latter is to determine whether or not the idling OFF state has occurred a certain number of times or more. Here, when MA ≧ Mth and I ≧ Ith (S2080: YES), that is, although it is determined that (TU−TL) <Tth in S2060, a certain number of acceleration operations are performed. If the idle idle state has been exceeded for a certain number of times, it is determined that there is an abnormality, the abnormality flag FB is set to “1” in S2090, and then the process proceeds to S2100. On the other hand, if MA <Mth or I <Ith (S2080: NO), the process proceeds to S2100 without executing the process of S2090.
[0062]
In S2100, a flag processing request is issued to the abnormality confirmed object 200. Thereafter, the B abnormality detection process is terminated.
Further, C abnormality detection processing executed by the C water temperature sensor object 110c will be described based on the flowcharts of FIGS. This C abnormality detection process is to detect an abnormality based on the water temperature rise due to the acceleration operation, similar to the above-described B abnormality detection process. However, this abnormality detection method is stipulated by laws and regulations, and is based on a rise in water temperature when the vehicle travels with a constant acceleration / deceleration pattern.
[0063]
First, in step S3000, flag information is copied to a register. In subsequent S3010, it is determined whether or not the engine is being started. If it is determined that the engine is being started (S3010: YES), an initialization process is executed in S3020, and then the process proceeds to S3100 in FIG. In the initialization process of S3020, the pattern condition satisfaction flag Fp is set to “0”, the minimum water temperature TL and the maximum water temperature TU are initialized as the water temperature at the time of starting the engine, respectively, and further the water temperature at the time of starting the engine Is assigned. On the other hand, if it is determined that the engine is not being started (S3010: NO), the process proceeds to S3030.
[0064]
In S3030, it is determined whether the pattern condition is satisfied. This pattern is defined by laws and regulations, and is a constant acceleration / deceleration pattern such as acceleration travel → steady travel → first deceleration travel → steady travel → second deceleration travel. Therefore, it is determined here whether or not the trajectory of the traveling pattern matches this acceleration / deceleration pattern. If it is determined that the pattern condition is satisfied (S3030: YES), the pattern condition satisfaction flag Fp is set to “1” in S3040, and then the process proceeds to S3050. On the other hand, when it is determined that the pattern condition is not satisfied (S3030: NO), the processing of S3040 is not executed, and the process proceeds to S3050.
[0065]
In S3050, the minimum water temperature TL and the maximum water temperature TU are updated. In this process, as in S2230 in FIG. 9, if the minimum water temperature TL is higher than the current water temperature, the current water temperature is substituted for the minimum water temperature TL, while if the maximum water temperature TU is lower than the current water temperature, the current water temperature is set to the maximum water temperature TU. Is substituted.
[0066]
In subsequent S3060, it is determined whether or not the difference (TU−TL) between the maximum water temperature TU and the minimum water temperature TL is equal to or greater than the water temperature deviation determination value Tth. That is, it is determined here whether or not there has been a certain increase in water temperature. Here, if (TU−TL) ≧ Tth (S3060: YES), it is determined to be normal, the abnormality flag FC is set to “0” (S3070), and then the process proceeds to S3080. On the other hand, if (TU-TL) <Tth (S3060: NO), the processing of S3070 is not executed, and the processing proceeds to S3080.
[0067]
In S3080, it is determined whether or not the pattern condition satisfaction flag Fp is “1”. Further, it is determined whether or not the difference (TU−TL) between the maximum water temperature TU and the minimum water temperature TL is smaller than the water temperature deviation determination value Tth. Here, when Fp = 1 and (TU−TL) <Tth (S3080: YES), that is, when a constant water temperature rise is not seen even though the vehicle has traveled in a predetermined acceleration / deceleration pattern, Since it is abnormal, the abnormality flag FC is set to “1” (S3090), and the process proceeds to S3100 in FIG. On the other hand, if Fp = 0 or (TU−TL) ≧ Tth (S3080: NO), the process of S3090 is not executed, and the process proceeds to S3100 in FIG.
[0068]
In S3100 in FIG. 11, the minimum water temperature TL and the maximum water temperature TU are updated. This process is the same as S3050 in FIG. 10 described above.
In subsequent S3110, it is determined whether or not the difference (TU−TL) between the maximum water temperature TU and the minimum water temperature TL is equal to or greater than a second water temperature deviation determination value T2th. The second water temperature deviation determination value T2th is for determining an increase in the water temperature when straddling a trip. If (TU-TL)> T2th (S3110: YES), the abnormality flag FC is set to “0” as normal, and the current water temperature is substituted to reset the minimum water temperature TL and the maximum water temperature TU. (S3120), and then the process proceeds to S3130. On the other hand, if (TU−TL) ≦ T2th (S3110: NO), the process of S3120 is not executed, and the process proceeds to S3130.
[0069]
In S3130, a flag processing request is issued to the abnormality confirmed object 200. Thereafter, the C abnormality detection process is terminated.
Next, the abnormality confirmation process (S2) executed by the abnormality confirmation object 200 will be described based on the flowchart of FIG.
[0070]
Low voltages 1 to 3 in S4000, S4010, and S4020 are flag information, set to “0” or “1”, and sent from the abnormality detection object 100 together with the flag processing request.
For example, in the case of detecting an abnormality of the water temperature sensor 20, when the voltage + B of the battery 19 decreases, the signal value from the water temperature sensor 20 is fixed even though the water temperature sensor 20 is normal. Therefore, the water temperature sensor object 110 sets the low voltage 3 to “1”. As a result, when the voltage + B of the battery 19 decreases to be equal to or lower than the voltage V, an affirmative determination is made in S4020, and the abnormality determination flag is set to “0” (S4030). That is, it is determined that there is no substantial abnormality. Since the rotation sensor that detects the rotation signal of the engine is not related to the voltage + B of the battery 19, the abnormality detection object 100 that detects abnormality of the rotation sensor sets the low voltage 3 to “0” and sends it out.
[0071]
In this way, each abnormality detection object 100 transmits flag information of low voltage 1 to 3, and the abnormality detection result of each abnormality detection object 100 can be processed in common processing steps (S4000 to S4020).
That is, in the determination process in S4000, when the signal IG from the ignition switch 26 is off and the low voltage 1 is set to “1” (S4000: YES), it is determined that there is no abnormality and the process proceeds to S4030. In the determination process in S4010, if the signal STA from the starter switch 28 is on and the low voltage 2 is set to “1” (S4010: YES), it is determined that there is no abnormality and the process proceeds to S4030. Furthermore, in the determination process in S4020, when the voltage + B of the battery 19 is equal to or lower than the voltage V and the low voltage 3 is set to “1” (S4010: YES), it is determined that there is no abnormality and the process proceeds to S4030. .
[0072]
In S4040 that is shifted when all negative determinations are made in S4000 to S4020, it is determined whether or not the flag information has changed. This was saved by the anomaly detection object 100 (S1000 in FIG. 6, S2000 in FIG. 8, Figure S300 in 10 0 Refer to: Judged by comparing with past flag information. If it is determined that the flag information has changed (S4040: YES), the abnormality determination flag is set to “1” in S4050, an abnormality confirmation notification is given to the abnormality processing object 300 in S4060, and then The abnormality confirmation process is terminated. On the other hand, when it is determined that the flag information has not changed (S4040: NO), the process of S4050 and S4060 is not executed, and the abnormality determination process is terminated.
[0073]
Next, the abnormal code storage process (S4) and abnormal code mask process (S5) executed by the abnormal code storage object 400 will be described with reference to the flowcharts of FIGS.
In the abnormal code storage process shown in FIG. 13, it is first determined whether or not there is an empty area in the standby RAM of the memory 39 (S5000). If it is determined that there is a free area (S5000: YES), the process proceeds to S5010. On the other hand, when it is determined that there is no free space (S5000: NO), the following process is not executed and the abnormal code storage process is terminated.
[0074]
In S5010, it is determined whether or not the abnormal code to be stored is already stored. If already stored (S5010: YES), the process of S5020 is not executed, and the abnormal code storage process is terminated. On the other hand, if not yet stored (S5010: NO), the abnormal codes are sorted in ascending order and stored in the standby RAM of the memory 39 (S5020), and then the abnormal code storage process is terminated.
[0075]
In the abnormal code masking process shown in FIG. 14, it is first determined whether or not the abnormal code to be masked is “0000” in hexadecimal notation. This is a failure prevention process performed because “0000” is stored in the free space. If the mask target is “0000” (S6000: YES), the subsequent process is not executed and the abnormal code mask process is terminated. On the other hand, if the mask target is other than “0000” (S6000: NO), the process proceeds to S6010.
[0076]
In S6010, it is determined whether an abnormal code to be masked is stored. If the abnormal code to be masked is not stored (S6010: NO), the process of S6020 is not executed and the abnormal code mask process is terminated. On the other hand, if an abnormal code to be masked is stored (S6010: YES), the abnormal code is masked in S6020. In other words, a flag corresponding to the abnormal code is set so that the abnormal code cannot be read. Thereafter, the abnormal code mask process is terminated.
[0077]
The effect which the engine control unit 16 of a present Example exhibits by having comprised each object 100-400 as mentioned above is described below.
In the engine control unit 16 of the present embodiment, when the abnormality detection object 100 executes the abnormality detection process (S1) (see FIG. 5), the abnormality is not detected for 20 trips after the abnormality is detected once. (S1120 in FIG. 7: YES), a mask processing request for the abnormal time processing object 300 is issued (S1140). The abnormal process object 300 executes the abnormal process (S3) and issues an abnormal code mask request, whereby the abnormal code storage object 400 executes the abnormal code mask process (S5). In this process (S5), as shown in FIG. 14, an abnormal code corresponding to a diagnosis target is searched (S6010), and the abnormal code is masked for each diagnosis target (S6020). In other words, if the detected abnormality is temporary, Vs For each elephant, the stored abnormal code is masked at a relatively early timing such as 20 trips. As a result, it is possible to prevent an abnormal code from being read out at a repair shop, for example, and a part that does not need to be replaced from being replaced.
[0078]
Further, as described above with the water temperature sensor object 110 as an example, the three water temperature sensor objects 110a, 110b, and 110c of A to C are provided corresponding to a plurality of abnormality detection methods. Of the three water temperature sensor objects 110a, the mask process request is made, but only when the water temperature sensor objects 110b and 110c of both B and C are not detected abnormally (S1130 in FIG. 7). : YES), a mask processing request is issued (S1140). Therefore, the abnormality code is not masked when the abnormality is detected in the water temperature sensor objects 110b and 110c of B or C just because the abnormality detection is not performed in the A water temperature sensor object 110a. .
[0079]
Furthermore, the abnormality detection object 100 is configured to execute an abnormality detection process that depends on a diagnosis target, and in addition, an object that issues a mask process request by determining the abnormality detection results of the water temperature sensor objects 110b and 110c of B and C. The A water temperature sensor object 110a which is the abnormality detection object 100 is also used. Therefore, when the diagnosis target is changed, only the abnormality detection object 100, that is, the three water temperature sensor objects 110a to 110c of A to C, the intake air temperature sensor object 120, the throttle sensor object 130, etc. may be changed. The fixed object 200, the abnormal time processing object 300, and the abnormal code storage object 400 need not be changed at all. Therefore, reusability of the self-diagnosis program can be ensured.
[0080]
A configuration in which the three water temperature sensor objects 110a to 110c A to C refer to the abnormality detection results and issue a mask processing request to each other is also conceivable, but the water temperature sensor object 110a is a water temperature sensor for B and C. It is sufficient to issue a mask processing request with reference to the abnormality detection results of the objects 110b and 110c. The reason is that there is a relatively high possibility that an abnormality is detected in the A abnormality detection process executed by the A water temperature sensor object 110a as compared with the B or C abnormality detection process. This is because if the abnormality of the sensor 20 is not detected, the possibility that an abnormality is detected in the abnormality detection process for B or C is small. In this embodiment, since only the A water temperature sensor object 110a has a process for issuing a mask processing request (S1060, S1080, S1090, S1100 in FIG. 6, S1120, S1130, S1140 in FIG. 7), the self-diagnosis is performed. When the program is viewed in total, it is advantageous in that the processing program is simplified, and that the determination processing is reduced and the processing load is reduced.
[0081]
By the way, it can also be set as the structure which the abnormality detection object 100 performs each abnormality confirmation process performed with the abnormality confirmation object 200. FIG. However, since the abnormality confirmation process is a common process when an abnormality is detected, in this embodiment, the abnormality confirmation object 200 is executed. As a result, the configuration of the self-diagnosis program is simplified, and when the abnormality detection object 100 is changed by changing the diagnosis target, it is not necessary to create / change this common processing, so that further reusability can be achieved. it can.
[0082]
In this embodiment, the abnormality processing object 300 is provided. This abnormality processing object 300 issues not only an abnormal code storage / mask request, but also a request for turning on / off the warning lamp 25 (see FIG. 3), and the warning lamp 25 is turned on / off by an object not shown. . Since the configuration is provided with the abnormal-time processing object 300 that supervises such abnormal-time processing, in this embodiment, the overall configuration of the self-diagnosis program is easily understood and expandability is enhanced.
[0083]
As described above, the present invention is not limited to such an embodiment, and can be implemented in various forms without departing from the gist of the present invention.
For example, in the above embodiment, the abnormal code is masked so that it cannot be read out. In this case, since the abnormal code remains in the standby RAM of the memory 39, it cannot be read by a normal operation at a repair shop or the like, but the abnormal information can be read and referred to by performing a special operation. Is advantageous. On the other hand, it is possible to adopt a configuration in which the abnormal code stored in the standby RAM of the memory 39 is deleted.
[0084]
In the above embodiment, the abnormal code is stored in the standby RAM in the memory 39. However, any memory device may be used as long as the stored contents are not lost even when the ignition switch is turned off. I can't. For example, an abnormal code may be stored in the EEPROM.
[Brief description of the drawings]
FIG. 1 is a configuration diagram illustrating an engine control system according to an embodiment.
FIG. 2 is a block diagram illustrating a configuration of an engine control unit according to the embodiment.
FIG. 3 is an explanatory diagram conceptually showing the structure of a self-diagnosis program.
FIG. 4 is an MSC showing an abnormal code storage procedure;
FIG. 5 is an MSC showing an abnormal code masking procedure;
FIG. 6 is a flowchart showing the first half of an A abnormality detection process.
FIG. 7 is a flowchart showing the latter half of A abnormality detection processing;
FIG. 8 is a flowchart showing B abnormality detection processing;
FIG. 9 is a flowchart showing calculation target value update processing;
FIG. 10 is a flowchart showing the first half of C abnormality detection processing;
FIG. 11 is a flowchart showing the latter half of the C abnormality detection process.
FIG. 12 is a flowchart showing abnormality confirmation processing.
FIG. 13 is a flowchart showing an abnormal code storage process.
FIG. 14 is a flowchart showing an abnormal code mask process.
[Explanation of symbols]
11 ... Engine
12 ... Intake pipe
13 ... Air flow sensor
14 ... Intake air temperature sensor
15 ... Throttle valve
16 ... Engine control unit
17 ... Throttle sensor
18. Air-fuel ratio sensor
19 ... Battery
20 ... Water temperature sensor
21 ... Distributor
22a, 22b, 22c, 22d
... injector
23 ... Igniter
24 ... Test switch
25 ... Warning light
26 ... Ignition switch
27 ... Starter motor
28 ... Starter switch
32 ... Analog input circuit
33. Digital input circuit
34 ... A / D converter
35 ... Power supply circuit
36, 37, 38
... Output circuit
39 ... Memory
100: Anomaly detection object
110 ... Water temperature sensor object
110a ... A water temperature sensor object
110b ... B water temperature sensor object
110c ... C water temperature sensor object
120: Intake air temperature sensor object
130: Throttle sensor object
200: Anomaly confirmation object
300 ... Abnormal processing object
400: Abnormal code storage object

Claims (5)

Based on the abnormality detection result of the diagnosis target, it has a self-diagnosis function that stores information at the time of abnormality corresponding to the diagnosis target,
A self-diagnostic program for realizing the self-diagnosis function is used for each diagnosis target and executes a process for detecting an abnormality of the diagnosis target. in the vehicle control apparatus configured in the object group that performs a treatment you store the abnormality information based on the abnormality detection result by the abnormality detection object,
When there are a plurality of methods for detecting an abnormality of the same diagnosis target, the abnormality detection object is prepared for each of the plurality of methods, and at least one of the abnormality detection objects is subjected to abnormality detection once. When a predetermined condition is satisfied, an instruction is given to invalidate the abnormality information only when no abnormality is detected in another abnormality detection object related to the same diagnosis target,
On the other hand, the control unit for a vehicle having a self-diagnosis function, wherein the object group invalidates the abnormality time information when an instruction to invalidate the abnormality time information is given from the abnormality detection object. The vehicle control device according to claim 1,
The abnormality detection object for instructing invalidity information of the abnormality is an object that performs abnormality detection by a method having a relatively high possibility of detecting abnormality among abnormality detection objects related to the same diagnosis target. A vehicle control device having a characteristic self-diagnosis function. The vehicle control device according to claim 1 or 2,
The object group is at least:
An abnormality confirmation object for determining whether or not there is a substantial abnormality based on an abnormality detection result by the abnormality detection object;
When an abnormality determination is made in the abnormality confirmation object, an abnormality processing object that makes a storage request for the abnormality information,
A vehicle control apparatus having a self-diagnosis function, comprising: an abnormality information storage object that stores the abnormality information according to the abnormality information storage request by the abnormality processing object. The vehicle control device according to claim 3,
When there is an invalid instruction for the abnormal time information from the abnormal detection object, the abnormal time processing object makes an invalid request for the abnormal time information,
The vehicle control device having a self-diagnosis function, wherein the abnormal time information storage object invalidates the abnormal time information in accordance with a request for invalidation of the abnormal time information by the abnormal time processing object. The computer-readable recording medium which recorded the said self-diagnosis program of the control apparatus for vehicles in any one of Claims 1-4.

Images