Abnormality diagnosis device

Abstract

To provide an abnormality diagnostic device capable of reliably storing abnormality data if an engine stall immediately after a start-up of an engine is not caused by running out of fuel.SOLUTION: An abnormality diagnostic device comprises: a sensor which detects a residual amount of fuel; and a control unit which receives residual amount data on the residual amount of fuel from the sensor through an on-vehicle network and stores abnormality data in a predetermined storage area when detecting an engine stall occurring with the residual fuel amount equal to or greater than a predetermined threshold. When detecting the engine stall occurring within a period from a start-up of an engine of a vehicle to a first reception of the residual amount data, the control unit stores occurrence of the engine stall. When the occurrence of the engine stall is stored and the residual amount of fuel indicated by the residual amount data received after the start-up of the engine is equal to or greater than a threshold, the control unit stores the abnormality data in the predetermined storage area.SELECTED DRAWING: Figure 3

Description

[Technical Field]

[0001] The present invention relates to an abnormality diagnosis device that stores abnormality data when it detects that the remaining fuel amount is equal to or greater than a threshold amount and that an engine stall has occurred. [Background technology]

[0002] Conventionally, there have been known abnormality diagnosis devices that store abnormality data indicating the occurrence of an engine stall (hereinafter referred to as "stalling"). For example, the abnormality diagnosis device described in Patent Document 1 (hereinafter referred to as "the conventional device") determines whether the fuel pressure is equal to or higher than a predetermined threshold pressure when an engine stall occurs. The conventional device stores abnormality data when the fuel pressure is equal to or higher than the threshold pressure. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Publication No. 2020-176523 Summary of the Invention

[0004] The inventors are considering an abnormality diagnosis device that stores abnormality data when the remaining fuel amount is equal to or greater than a threshold amount and the engine stalls, in order to prevent abnormality data from being stored when an engine stalls due to running out of gas.

[0005] In such an abnormality diagnosis device, it is desirable to store abnormality data even when an engine stall occurs immediately after starting. Generally, a sensor that detects the remaining fuel amount and a control unit that stores the abnormality data are connected via an in-vehicle network. Therefore, immediately after starting the engine, there is a high possibility that the control unit will not be able to receive the remaining fuel amount data due to communication delays in the in-vehicle network. Therefore, if an engine stall occurs between starting the engine and receiving the remaining fuel amount data, there is a possibility that the remaining fuel amount cannot be determined and the abnormality data cannot be stored.

[0006] The present invention has been made to address the above-mentioned problems. That is, one of the objects of the present invention is to provide an abnormality diagnosis device that can reliably store abnormality data when an engine stall that occurs immediately after starting the engine is not due to a lack of gas.

[0007] The abnormality diagnosis device of the present invention (hereinafter referred to as "the device") comprises: a fuel level sensor (32) for detecting the amount of fuel remaining in the vehicle; a control unit (20) that receives remaining fuel amount data indicating the remaining fuel amount from the sensor via an in-vehicle network (40), and stores abnormality data in a predetermined storage area (26a) when the remaining fuel amount is equal to or greater than a predetermined threshold amount and an occurrence of an engine stall is detected; The control unit If the occurrence of the engine stall is detected during the period from when the engine of the vehicle is started until the remaining amount data is first received (step 305 "Yes", step 315 "Yes"), the occurrence of the engine stall is stored (step 320), If the occurrence of the engine stall is stored in the storage area (step 330 "Yes"), and the remaining fuel amount indicated by the remaining fuel amount data received after the engine start is equal to or greater than the threshold amount (step 335 "Yes", step 340 "Yes"), the abnormality data is stored in the storage area (step 345). It is structured as follows.

[0008] If the control unit of this device detects an engine stall during the period from engine start to receiving the remaining fuel amount data, it stores that fact. If the control unit receives remaining fuel amount data after storing the fact of the engine stall, and the remaining fuel amount is equal to or greater than the threshold amount, it stores abnormality data. This allows the device to reliably store abnormality data if the engine stall that occurred during the period from engine start to receiving the remaining fuel amount data is not due to running out of gas. [Brief explanation of the drawings]

[0009] [Figure 1] 1 is a schematic system configuration diagram of an abnormality diagnosis device according to an embodiment of the present invention; [Figure 2] 2 is a flowchart of a remaining amount data receiving routine executed by a CPU of the engine ECU shown in FIG. 1. [Figure 3] 2 is a flowchart of an abnormality diagnosis routine executed by a CPU of the engine ECU shown in FIG. 1. DETAILED DESCRIPTION OF THE INVENTION

[0010] The abnormality diagnosis device 10 according to this embodiment includes the components shown in FIG. 1 and is applied to a vehicle VA.

[0011] In this specification, an "ECU" is an electronic control device that includes a microcomputer as its main component. The ECU is also called a control unit. The microcomputer includes a CPU (processor), ROM, RAM, an interface, and the like.

[0012] The engine ECU 20 is connected to an engine actuator 22 and controls the engine actuator 22. The engine actuator 22 changes the driving force generated by an engine 24 of the vehicle VA. Furthermore, the engine ECU 20 is connected to a storage device 26. The storage device 26 has a non-volatile storage area, and an abnormality data storage unit 26a is set in this storage area.

[0013] When an engine stall (hereinafter referred to as "stalling") occurs in the engine 24, and the stall is not due to a lack of gas, the engine ECU 20 stores abnormality data indicating that fact in the abnormality data storage unit 26a.

[0014] The meter ECU 30 is connected to a fuel amount sensor 32. The fuel amount sensor 32 detects a remaining fuel amount RA that indicates the amount of fuel remaining in a fuel tank .

[0015] The engine ECU 20 and the meter ECU 30 are connected via an in-vehicle network 40. The meter ECU 30 determines the remaining fuel amount RA based on the detection value of the remaining fuel amount sensor 32 every time a predetermined time elapses, and transmits remaining amount data indicating the remaining fuel amount RA to the engine ECU 20.

[0016] (Overview of operation) When engine ECU 20 receives remaining amount data from meter ECU 30, it determines the remaining fuel amount RA based on the remaining amount data. When engine ECU 20 detects an engine stall, it determines whether the remaining fuel amount RA is equal to or greater than a predetermined threshold amount RAth. If the remaining fuel amount RA is equal to or greater than the threshold amount RAth, engine ECU 20 determines that the engine stall is not due to a lack of gas, and stores abnormality data in abnormality data storage unit 26a.

[0017] When an ignition key switch (not shown) is changed from the OFF position to the ON position, the engine ECU 20 starts the engine 24. Immediately after the engine 24 starts, the engine ECU 20 is unable to receive remaining fuel data due to delays in the in-vehicle network. Even if the engine ECU 20 detects an engine stall during this period, it is unable to determine whether the engine stall is due to a lack of gas because it is unable to identify the remaining fuel amount RA.

[0018] Therefore, if engine ECU 20 detects an engine stall during the period from when engine 24 is started until the engine ECU 20 first receives the remaining amount data, it stores the fact (specifically, it sets the value of engine stall flag Xes to "1"). If engine ECU 20 subsequently receives remaining amount data, and the remaining fuel amount RA indicated by the remaining amount data is equal to or greater than the threshold amount RAth, engine ECU 20 stores abnormality data in abnormality data storage unit 26a.

[0019] This ensures that abnormality data can be stored if the engine stall that occurred between the start of the engine and the reception of the remaining amount data is not due to a lack of gas.

[0020] (Specific operation) <Remaining amount data reception routine> The CPU of the engine ECU 20 (hereinafter referred to as "CPU") executes a routine shown in the flowchart of FIG. 2 every time a predetermined time period elapses.

[0021] When an appropriate time arrives, the CPU starts processing from step 200 in FIG. 2, and in step 205 determines whether remaining amount data has been received during the period from the previous execution of this routine to the current execution of this routine.

[0022] If the remaining amount data has not been received, the CPU determines "No" in step 205 and ends this routine in step 295.

[0023] If the remaining amount data has been received, the CPU determines "Yes" in step 205 and executes steps 210 and 215. Step 210: The CPU identifies the remaining fuel amount RA represented by the remaining amount data. Step 215: The CPU determines whether the value of the reception flag Xrec is "0".

[0024] The value of the reception flag Xrec is set to "0" in the initial routine, and is set to "1" when the engine ECU 20 receives remaining amount data for the first time after starting the engine 24. The initial routine is executed when the ignition key switch is changed from the OFF position to the ON position.

[0025] If the value of the reception flag Xrec is "0", the CPU determines "Yes" in step 215 and sets the value of the reception flag Xrec to "1" in step 220. After that, in step 295, the CPU temporarily ends this routine.

[0026] If the value of the reception flag Xrec is "1", the CPU does not execute step 220 and ends this routine at step 295.

[0027] <Abnormality diagnosis routine> The CPU executes the routine shown in the flowchart of FIG. 3 every time a predetermined time elapses.

[0028] When an appropriate time arrives, the CPU starts processing from step 300 in FIG. 3, and in step 305 detects whether an engine stall has occurred during the detection period from the previous execution of this routine to the current execution of this routine.

[0029] If an engine stall occurs during the above detection period, the CPU determines "Yes" in step 305 and executes steps 310 and 315. Step 310: The CPU acquires behavior data of the vehicle VA. The behavior data includes at least one of the vehicle speed, the shift position, the accelerator pedal operation amount, and the brake pedal operation amount, for example. Step 315: The CPU determines whether the value of the reception flag Xrec is "0".

[0030] If the value of the reception flag Xrec is "0", the CPU determines "Yes" in step 315 and executes steps 320 to 330. Step 320: The CPU sets the value of the engine stall flag Xes to “1”. Step 325: The CPU temporarily stores the behavior data acquired in step 310. Temporarily storing means that the CPU stores the data in a RAM, for example. Step 330: The CPU determines whether the value of the engine stall flag Xes is "1".

[0031] The value of the engine stall flag Xes is set to "0" in the initial routine and in step 350 described later, and is set to "1" if an engine stall occurs during the period from when the engine 24 is started until the engine ECU 20 receives the remaining amount data.

[0032] If the value of the engine stall flag Xes is "1", the CPU determines "Yes" in step 330, and determines in step 335 whether the value of the reception flag Xrec is "1".

[0033] If the value of the reception flag Xrec is "0", the CPU determines "No" in step 335 and ends this routine in step 395.

[0034] If an engine stall has not occurred during the detection period the next time the CPU executes this routine, the CPU determines "No" in step 305 and proceeds to step 330. Since the value of the engine stall flag Xes is "1," the CPU determines "Yes" in step 330 and proceeds to step 335.

[0035] If the value of the reception flag Xrec is "1", the CPU determines "Yes" in step 335, and determines in step 340 whether the remaining fuel amount RA is equal to or greater than a predetermined threshold amount RAth.

[0036] If the remaining fuel amount RA is equal to or greater than the threshold amount RAth, the CPU determines "Yes" in step 340 and executes steps 345 and 350. Step 345: The CPU stores the abnormality data and the behavior data temporarily stored in step 325 in the abnormality data storage unit 26a. Step 350: The CPU sets the value of the engine stall flag Xes to “0”. Thereafter, the CPU temporarily ends this routine in step 395.

[0037] If the remaining fuel amount RA is less than the threshold amount RAth, the CPU determines "No" in step 340 and proceeds to step 355, where it erases the "temporarily stored behavior data." After that, the CPU executes step 350 and ends this routine in step 395.

[0038] On the other hand, if the value of the reception flag Xrec is "1" when an engine stall occurs, the CPU determines "No" in step 315 and determines in step 360 whether the remaining fuel amount RA is equal to or greater than a predetermined threshold amount RAth.

[0039] If the remaining fuel amount RA is equal to or greater than the threshold amount RAth, the CPU determines "Yes" in step 360 and stores the abnormality data and the behavior data acquired in step 310 in the abnormality data storage unit 26a in step 365. Thereafter, the CPU proceeds to step 330.

[0040] On the other hand, if the remaining fuel amount RA is less than the threshold amount RAth, the CPU determines "No" in step 360 and proceeds to step 330.

[0041] If the value of the engine stall flag Xes is "0" when the CPU proceeds to step 330, the CPU determines "No" in step 330 and temporarily ends this routine in step 395.

[0042] As described above, if an engine stall that occurs between the start of the engine 24 and the reception of the remaining fuel amount data is not due to a lack of gas, abnormality data can be reliably stored. Furthermore, in this embodiment, the CPU temporarily stores behavior data if an engine stall occurs between the start of the engine 24 and the reception of the remaining fuel amount data, and then stores the temporarily stored behavior data in the abnormality data storage unit 26a if the remaining fuel amount RA is equal to or greater than the threshold amount RAth upon receiving the remaining fuel amount data. This makes it possible to store behavior data at the time the engine stall occurred, even if the engine stall occurs between the start of the engine 24 and the reception of the remaining fuel amount data.

[0043] The following examples are examples of modifications of this embodiment. If the remaining fuel amount RA is equal to or greater than the "non-determination threshold amount RAth' set to a value equal to or greater than the threshold amount RAth" when the ignition key switch is changed from the on position to the off position, the CPU stores determination-free data in a non-volatile storage area. Thereafter, if the CPU detects an engine stall during the period from the start of the engine 24 until the engine ECU 20 receives the remaining fuel amount data, the CPU may immediately store abnormality data without determining whether the remaining fuel amount RA is equal to or greater than the threshold amount RAth, as long as the determination-free data is stored in the non-volatile storage area. [Explanation of symbols]

[0044] 10... Abnormality diagnosis device, 20... Engine ECU, 24... Engine, 26a... Abnormality data storage unit, 32... Remaining amount sensor, 40... In-vehicle network.

Claims

[Claim 1] a fuel level sensor that detects the amount of fuel remaining in the vehicle; a control unit that receives remaining fuel amount data indicating the remaining fuel amount from the sensor via an in-vehicle network, and stores abnormality data in a predetermined storage area when the remaining fuel amount is equal to or greater than a predetermined threshold amount and an engine stall is detected; The control unit If an occurrence of the engine stall is detected during the period from when the engine of the vehicle is started until when the remaining amount data is first received, the occurrence of the engine stall is stored in memory; When the occurrence of the engine stall is stored and the remaining fuel amount indicated by the remaining fuel amount data received after the engine is started is equal to or greater than the threshold amount, the abnormality data is stored in the storage area. The abnormality diagnosis device is configured as follows.

Images