Abnormality diagnostic device
The abnormality diagnosis device addresses the issue of unreliable data storage during engine startup by using a control unit to store data only if the fuel amount exceeds a threshold and an engine stall occurs, ensuring accurate data capture of non-gas-related engine stalls.
Patent Information
- Application Number
- JP2023078721
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2023-05-11
- Publication Date
- 2024-11-21
- Estimated Expiration
- 2043-05-11
AI Technical Summary
Existing abnormality diagnosis devices fail to reliably store abnormality data when an engine stall occurs immediately after engine start due to potential delays in receiving fuel remaining amount data via an in-vehicle network, leading to uncertainty about whether the stall is gas-related.
An abnormality diagnosis device that includes a sensor to detect remaining fuel amount and a control unit to store abnormal data only if the detected amount is above a threshold and an engine stall is detected during the initial engine startup phase, ensuring data storage even if the stall is not gas-related.
Ensures reliable storage of abnormal data during engine startup by determining the fuel amount post-stall, preventing false data storage and maintaining accurate records of non-gas-related engine stalls.
Smart Images

Figure 2024162810000001_ABST
Abstract
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 has been known an abnormality diagnosis device that stores 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 or not 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] JP 2020-176523 A 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 abnormal data from being stored when a stall occurs due to running out of gas.
[0005] In such an abnormality diagnosis device, it is desirable to store abnormality data even when the engine stalls immediately after starting. In general, a sensor that detects the remaining fuel amount and a control unit that stores the abnormality data are connected via an in-vehicle network, so that immediately after starting the engine, the control unit is likely not to receive the remaining fuel amount data due to a communication delay in the in-vehicle network. Therefore, if the engine stalls during the period from when the engine starts to when the remaining fuel amount data is received, the remaining fuel amount cannot be identified and therefore the abnormality data may not 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 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 representing 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); When the occurrence of the engine stall is stored in the storage area (step 330 “Yes”), and the remaining fuel amount represented by the remaining fuel amount data received after the engine is started 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 the device detects an engine stall during the period from engine start to receiving the remaining fuel amount data, the control unit stores the occurrence. If the control unit receives remaining fuel amount data after storing the occurrence of the engine stall, and the remaining fuel amount is equal to or greater than the threshold amount, the control unit 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 a lack of gas. [Brief description 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. [Diagram 2] 2 is a flowchart of a remaining amount data receiving routine executed by a CPU of the engine ECU shown in FIG. 1. [Diagram 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 PREFERRED EMBODIMENTS
[0010] An 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, "ECU" refers to 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, and an interface.
[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 the storage area.
[0013] When an engine stall (hereinafter referred to as "stalling") occurs in the engine 24, and the stall is not due to 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 specifies 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 the engine ECU 20 receives the remaining amount data from the meter ECU 30, the engine ECU 20 specifies the remaining fuel amount RA based on the remaining amount data. When the engine ECU 20 detects the occurrence of an engine stall, the engine ECU 20 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, the engine ECU 20 determines that the engine stall is not due to a lack of gas, and stores the abnormality data in the 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. Due to a delay time of the in-vehicle network, the engine ECU 20 cannot receive the remaining amount data immediately after starting the engine 24. Even if the engine ECU 20 detects the occurrence of an engine stall during this period, it cannot determine whether the engine stall is due to a lack of gas because it cannot 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 the stall flag Xes to "1.") If engine ECU 20 subsequently receives remaining amount data, and if the remaining fuel amount RA represented by the remaining amount data is equal to or greater than the threshold amount RAth, it stores abnormality data in abnormality data storage unit 26a.
[0019] This makes it possible to reliably store abnormality data if the engine stall that occurs 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 data reception routine> The CPU of the engine ECU 20 (hereinafter referred to as the "CPU") executes a routine shown in the flowchart of FIG. 2 every time a predetermined time elapses.
[0021] When an appropriate time arrives, the CPU starts the process from step 200 in FIG. 2, and in step 205 determines whether or not 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 makes a “No” determination in step 205 and terminates this routine in step 295.
[0023] If 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" or not.
[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 the process from step 300 in FIG. 3, and in step 305 detects whether or not 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" or not.
[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 behavior 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 the engine stalls 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 judges "Yes" in step 330, and then judges 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 makes a "No" determination in step 335 and terminates 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 then 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 to erase the "provisionally 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 the engine stalls, 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 judges “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. After that, 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 makes a “No” determination 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 makes a "No" determination in step 330 and terminates this routine in step 395.
[0042] As described above, if the engine stall that occurs during the period from when the engine 24 is started until the remaining amount data is received 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 the engine stalls during the period from when the engine 24 is started until the remaining amount data is received, and then, if the remaining amount data is received and the remaining fuel amount RA is equal to or greater than the threshold amount RAth, stores the temporarily stored behavior data in the abnormality data storage unit 26a. As a result, even if the engine stalls during the period from when the engine 24 is started until the remaining amount data is received, the behavior data at the time the engine stalled can be stored.
[0043] The following are examples of modifications of this embodiment. If the remaining fuel amount RA is equal to or greater than the "non-determinable 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 the non-determinable data in a non-volatile storage area. If the CPU detects an engine stall during the period from when the engine 24 is started until the engine ECU 20 receives the remaining amount data, the CPU may immediately store the abnormality data without determining whether the remaining fuel amount RA is equal to or greater than the threshold amount RAth if the non-determinable data has been 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 indicative of the amount of fuel remaining in the vehicle; a control unit that receives remaining fuel amount data representing 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 occurrence of an engine stall is detected; The control unit if an occurrence of the engine stall is detected during a period from when the engine of the vehicle is started until the remaining amount data is first received, storing the occurrence of the engine stall; when the occurrence of the engine stall is stored and the remaining fuel amount represented by the remaining fuel amount data received after the start of the engine 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.
Citation Information
Patent Citations
Troubleshooting control device for vehicle
JP2004044407A
Residual oil quantity display
JP2010160085A
Starting control device for internal combustion engine
JP2013108426A
Vehicle diagnosis device
JP2020133546A
Diagnostic data processor
JP2020176523A
