Driving Support Devices

The driving support device adjusts collision thresholds based on driver state duration to accurately execute braking/driving force control during minor collisions, reducing secondary damage and annoyance.

JP7582240B2Active Publication Date: 2024-11-13TOYOTA JIDOSHA KK
View PDF 4 Cites 0 Cited by

Patent Information

Application Number
JP2022061999
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Filing Date
2022-04-01
Publication Date
2024-11-13
Estimated Expiration
2042-04-01

AI Technical Summary

Technical Problem

Conventional driving support devices inaccurately execute braking/driving force control during light collisions, particularly when the driver is not drowsy, leading to potential driver annoyance and incorrect threshold settings.

Method used

A driving support device that adjusts the light collision threshold based on the elapsed time since the driver was detected in a singular state, such as drowsiness or incorrect acceleration, to increase the likelihood of executing braking/driving force control during minor collisions while minimizing driver annoyance.

Benefits of technology

The device effectively executes braking/driving force control during minor collisions, reducing secondary damage and minimizing driver annoyance by accurately determining the need for such control based on the driver's state over time.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007582240000001
    Figure 0007582240000001
  • Figure 0007582240000002
    Figure 0007582240000002
  • Figure 0007582240000003
    Figure 0007582240000003
Patent Text Reader

Abstract

To reduce the possibility of drive force control causing a driver to feel cumbersome, while enhancing the possibility of the drive force control to be executed in a case where the vehicle collides with a guard rail, a curve stone or the like.SOLUTION: An operation support apparatus executes deployment control at least including control to deploy an airbag of a vehicle in a case where a collision index value meets a given collision condition, and executes brake-drive force control to reduce vehicular drive force than required drive force of a vehicular driver, or apply brake force to the vehicle, in a case where the collision index value does not meet the collision condition while meeting a given light collision condition that is established in a degree of collision lighter than the given collision condition. Further, the operation support apparatus makes the light collision condition easier to be established as an elapsed time, which represents the time that the driver has been kept in a singular state since a singular condition that the driver is in the singular state that the driver is not driving normally is established, becomes longer.SELECTED DRAWING: Figure 2
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present invention relates to a driving support device that performs damage mitigation control for mitigating damage caused by a vehicle collision. [Background technology]

[0002] 2. Description of the Related Art Conventionally, driving support devices that execute damage mitigation control in the event of a vehicle collision are known. As damage mitigation control, control for deploying an airbag (hereinafter referred to as "deployment control") is known.

[0003] In the event of a minor collision that is less severe than the "degree to which deployment control should be executed," it is desirable to execute braking / driving force control as damage mitigation control. Braking / driving force control is control that reduces the driving force of the vehicle below the driving force requested by the driver or applies a braking force to the vehicle in order to reduce secondary damage caused by the vehicle moving after the collision and colliding with another object. This braking / driving force control is sometimes called "secondary damage mitigation control." It is desirable that the threshold value used to determine whether or not to execute the above-mentioned braking / driving force control (in other words, the threshold value used to determine whether or not a minor collision has occurred, hereinafter referred to as the "minor collision threshold") is set to a relatively small value so that braking / driving force control is executed even when the vehicle collides with a guardrail, a curb, etc.

[0004] However, if the light collision threshold is set to a relatively small value, there is a possibility that the braking / driving force control will be erroneously executed even if no light collision has occurred when the vehicle is traveling on a rough road, etc. For this reason, the light collision threshold is set to a relatively high value.

[0005] For example, the driving assistance device described in Patent Document 1 (hereinafter referred to as the "conventional device") executes braking / driving force control if the driver is dozing off when the collision index value, which indicates the severity of the collision, becomes equal to or exceeds the minor collision threshold value (i.e., when a minor collision occurs), but does not execute braking / driving force control if the driver is not dozing off. [Prior art documents] [Patent documents]

[0006] [Patent Document 1] Patent Publication No. 2021-112983 Summary of the Invention

[0007] In the conventional device, the condition that the driver is dozing off is a necessary condition for executing the braking / driving force control. Therefore, even if the braking / driving force control is executed by mistake, the braking / driving force control calls the attention of the dozing driver, so the driver is unlikely to feel bothered by the braking / driving force control. Therefore, the light collision threshold can be set to a relatively low value.

[0008] However, the conventional device may erroneously determine that the driver is dozing off even when the driver is not dozing off. If such an erroneous determination is made and braking / driving force control is erroneously performed, the driver is likely to find the braking / driving force control annoying.

[0009] 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 a driving assistance device that can increase the possibility that braking / driving force control is executed when the vehicle collides with a guardrail, a curb, or the like, while reducing the possibility that the driver will find the braking / driving force control bothersome.

[0010] The driving assistance device of the present invention (hereinafter referred to as the "device of the present invention") is an acceleration sensor (24) configured to measure an acceleration (G) acting on a body of a vehicle (VA); a control unit (20, 30, 40) configured to execute damage mitigation control for mitigating damage caused by a collision when the vehicle collides; Equipped with The control unit When the collision index value, which is acquired based on the acceleration and indicates the severity of the collision of the vehicle, satisfies a predetermined collision condition (step 540 "Yes"), a deployment control including at least a control for deploying an airbag (62) of the vehicle is executed as the damage mitigation control (step 565), When the collision index value does not satisfy the collision condition but satisfies a predetermined minor collision condition that is satisfied when the collision is less severe than the collision condition (step 535 "Yes", step 545 "Yes"), the driving force of the vehicle is made smaller than the driving force requested by the driver of the vehicle, or a braking / driving force control that applies a braking force to the vehicle is executed as the damage mitigation control (step 550, steps 700 to 795). The longer the elapsed time that indicates the time that has elapsed since the specific condition that the driver is not driving normally and is in the specific state is established, the more likely the minor collision condition is established (steps 620 to 640). It was configured as follows: Driving assistance device.

[0011] According to the device of the present invention, the longer the elapsed time that the driver remains in the peculiar state from the point in time when the peculiar condition is established, the more likely it is that the minor collision condition will be established, and therefore the more likely it is that the braking / driving force will be executed when a minor collision occurs. As a result, the more likely it is that the driver is in the peculiar state, the more likely it is that the braking / driving force control will be executed when the vehicle collides with a guardrail, a curb, or the like. Even if the braking / driving force control is executed erroneously, this braking / driving force control will alert the driver who is likely to be in the peculiar state, and the driver will be less likely to feel that the braking / driving force is bothersome.

[0012] In one embodiment of the device of the present invention, The control unit If the collision index value is equal to or greater than the predetermined collision threshold (GAth) (step 540 "Yes"), the collision condition is established; When at least a first condition is satisfied that the collision index value is equal to or greater than a predetermined light collision threshold (GBth) that is set to a value smaller than the collision threshold and is less than the collision threshold (step 535 "Yes"), the light collision condition is satisfied, The longer the elapsed time is, the smaller the light collision threshold is set to make it easier for the light collision condition to be satisfied (steps 620, 625, and 635). It is structured as follows.

[0013] Thereby, the light collision threshold value is made smaller as the elapsed time increases, so that the light collision condition can be more reliably established as the elapsed time increases.

[0014] In the above aspect, The control unit is configured to establish the minor collision condition when the first condition is satisfied (step 535 "Yes") and the second condition is satisfied that the magnitude of the integral value of the collision index value is greater than or equal to a predetermined integral threshold (step 545 "Yes")

[0015] The magnitude of the integral value of the collision index value when a minor collision occurs tends to be larger than the magnitude of the integral value of the collision index value when the vehicle is traveling on a rough road. Therefore, according to the above aspect, it is possible to reduce the possibility of erroneously determining that the minor collision condition is satisfied when the vehicle is traveling on a rough road.

[0016] In the above aspect, The control unit is configured to make the light crash condition more likely to be met by decreasing the light crash threshold and the integral threshold as the elapsed time increases (steps 620 to 640).

[0017] Thereby, the light collision threshold value and the integral threshold value are made smaller as the elapsed time increases, so that the light collision condition can be more reliably established as the elapsed time increases.

[0018] In one embodiment of the device of the present invention, The control unit is configured to establish the special condition when the driver is in an erroneous operation state in which the driver erroneously operates the acceleration operator to accelerate the vehicle (step 410 ``Yes''), or when the driver is in a drowsy state (step 310 ``Yes'').

[0019] When the driver is operating the vehicle erroneously or is asleep, there is a high possibility that the driver is not driving normally. In such a case, the special condition is established, and the longer the time that has elapsed since the special condition was established, the easier it becomes for the minor collision condition to be established, so that the driving / braking force control can be executed for a minor collision, and the possibility that the driver will feel annoyed even if the driving / braking force control is executed erroneously can be reduced.

[0020] In the above description, in order to facilitate understanding of the invention, the names and / or symbols used in the embodiments described below are added in parentheses to the configurations of the invention corresponding to those embodiments. However, each component of the invention is not limited to the embodiments defined by the names and / or symbols. Other objects, other features, and associated advantages of the present invention will be easily understood from the following description of the embodiments of the present invention, which will be described with reference to the drawings. [Brief description of the drawings]

[0021] [Figure 1] FIG. 1 is a schematic system configuration diagram of a driving assistance device according to an embodiment of the present invention. [Diagram 2] FIG. 2 is an explanatory diagram of an outline of the operation of the driving support device according to the embodiment of the present invention. [Diagram 3] FIG. 3 is a flowchart showing a drowsiness determination routine executed by the CPU of the driving assistance ECU shown in FIG. [Figure 4] FIG. 4 is a flowchart showing an erroneous operation determination routine executed by the CPU of the driving assistance ECU shown in FIG. [Diagram 5] FIG. 5 is a flowchart showing a collision determination routine executed by the CPU of the driving assistance ECU shown in FIG. [Figure 6] FIG. 6 is a flowchart showing a threshold setting subroutine executed by the CPU of the driving assistance ECU shown in FIG. [Figure 7] FIG. 7 is a flowchart showing a first braking control routine executed by the CPU of the driving assistance ECU shown in FIG. [Figure 8] FIG. 7 is a flowchart showing a second braking control routine executed by the CPU of the driving assistance ECU shown in FIG. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0022] A driving assistance device (hereinafter referred to as "this assistance device") 10 according to one embodiment of the present invention is mounted on a vehicle VA. As shown in Fig. 1, this assistance device 10 includes a driving assistance ECU (hereinafter referred to as "DSECU") 20, a drive ECU 30, a brake ECU 40, and an alarm ECU 50. These ECUs are connected to each other via a controller area network (CAN) (not shown) so as to be able to exchange data (communicate).

[0023] ECU is an abbreviation of Electronic Control Unit, and is an electronic control circuit having a microcomputer including a CPU, ROM, RAM, and an interface (I / F) as its main components. The ECU may also be called a "control unit," "controller," or "computer." The CPU realizes various functions by executing instructions (routines) stored in the memory (ROM). All or some of the above ECUs 20 to 50 may be integrated into one ECU.

[0024] The DSECU 20 is connected to a plurality of wheel speed sensors 22, an acceleration sensor 24, and a driver's seat camera 26 so as to be able to exchange data.

[0025] The wheel speed sensor 22 is provided for each wheel of the vehicle VA, and generates one pulse signal each time the corresponding wheel rotates a predetermined angle. The DSECU 20 measures the number of pulses per unit time of the pulse signal generated by each wheel speed sensor 22, and obtains the rotation speed (wheel speed) of each wheel based on the measured number of pulses. The DSECU 20 obtains a vehicle speed Vs indicating the speed of the vehicle VA based on the rotation speed of each wheel. As an example, the average value of the rotation speeds of the four wheels is obtained as the vehicle speed Vs.

[0026] The acceleration sensor 24 measures the acceleration G of the body of the vehicle VA (the acceleration in the forward / rearward direction and the acceleration in the left / right direction of the vehicle VA). The acceleration sensor 24 generates a detection signal representing the acceleration G. The DSECU 20 identifies the acceleration G based on the detection signal generated by the acceleration sensor 24.

[0027] The driver's seat camera 26 captures a scene of an area including the position of the face of the driver of the vehicle VA when the driver sits in the driver's seat of the vehicle VA, thereby acquiring a driver's seat image. The driver's seat camera 26 transmits the driver's seat image to the DSECU 20.

[0028] The DSECU 20 is connected to an accelerator pedal operation amount sensor 32 and a drive source actuator 34 so as to be able to exchange data.

[0029] The accelerator pedal operation amount sensor 32 measures the operation amount of the accelerator pedal 32a of the vehicle VA (the amount of depression of the accelerator pedal 32a by the driver) and generates a detection signal representing this operation amount. Hereinafter, the operation amount of the accelerator pedal 32a is referred to as the "accelerator operation amount AP." The accelerator pedal 32a is an operator operated by the driver to accelerate the vehicle VA, and may also be referred to as the "acceleration operator."

[0030] The drive source actuator 34 is connected to a drive source (such as an electric motor or an internal combustion engine) 34a. The drive ECU 30 changes the operating state of the drive source 34a by controlling the drive source actuator 34. This allows the drive ECU 30 to adjust the drive force (drive force generated by the drive source 34a) applied to the vehicle VA. The drive ECU 30 controls the drive source actuator 34 so that the drive force applied to the vehicle VA increases as the accelerator operation amount AP increases.

[0031] The brake ECU 40 is connected to a brake pedal operation amount sensor 42 and a brake actuator 44 so as to be able to exchange data with each other.

[0032] The brake pedal operation amount sensor 42 measures the operation amount of the brake pedal 42a of the vehicle VA (the depression amount of the brake pedal 42a) and generates a detection signal representing this operation amount. Hereinafter, the operation amount of the brake pedal 42a is referred to as the "brake operation amount BP."

[0033] The brake actuator 44 is connected to a known hydraulic braking device 44a. The brake ECU 40 controls the brake actuator 44 to change the friction braking force generated by the braking device 44a. This allows the brake ECU 40 to adjust the braking force applied to the vehicle VA. The brake ECU 40 controls the brake actuator 44 so that the braking force applied to the vehicle VA increases as the brake operation amount BP increases.

[0034] The notification ECU 50 is connected to a display 52, a hazard lamp 54, and a speaker 56 so as to be able to exchange data with them. The display 52 is, for example, a multi-information display, and is disposed in a position facing the driver when the driver sits in the driver's seat. The display 52 has an erroneous operation indicator light and a drowsy driver indicator light, not shown. The erroneous operation indicator light is turned on when it is determined that the driver is erroneously operating the accelerator pedal 32a, and the drowsy driver indicator light is turned on when it is determined that the driver is drowsy. The hazard lamp 54 is turned on when it is determined that the driver is dozing. The speaker 56 issues an alarm sound when it is determined that the driver is dozing.

[0035] Furthermore, the DSECU 20 is connected to the inflator 60 so as to be able to exchange data with it. When the inflator 60 receives an ignition signal from the DSECU 20, it generates gas to deploy (inflate) the airbags 62. An appropriate number of airbags 62 are disposed at appropriate positions in the vehicle VA.

[0036] (Overview of operation) The support device 10 executes deployment control when a collision condition is met in which the magnitude of the acceleration G is equal to or greater than a predetermined collision threshold value GAth. The deployment control includes control for deploying the airbag 62 and braking control for applying a braking force to the vehicle VA. The acceleration G is a value that indicates the degree of collision of the vehicle VA, and may be referred to as a "collision index value." The collision index value is not limited to the acceleration G, and may be any value that is obtained based on the acceleration G. For example, the collision index value may be a value obtained by multiplying the mass of the vehicle VA by the acceleration G.

[0037] When the "light collision condition that the following first and second conditions are satisfied" is satisfied, the support device 10 determines that a "light collision that is less severe than the collision that satisfies the above-mentioned collision condition" has occurred. In this case, the support device 10 executes braking control to apply braking force to the vehicle VA. The braking control executed when the light collision condition is satisfied is referred to as the "first braking control" or "braking / driving force control," and the braking control of the deployment control executed when the collision condition is satisfied is referred to as the "second braking control." The "braking control executed when a minor collision condition is met" and the "deployment control executed when a collision condition is met" are controls for reducing damage during (or after) a collision, and are sometimes referred to as damage reduction control.

[0038] First condition: the magnitude of the acceleration G is equal to or greater than a predetermined light collision threshold GBth and is less than a collision threshold GAth. Second condition: The magnitude of the acceleration integral value V, which is the integral value of the acceleration G, is equal to or greater than an integral threshold value Vth. The light collision threshold GBth is set to a value smaller than the collision threshold GAth.

[0039] The support device 10 judges whether a special condition that indicates a special state in which the driver cannot drive normally is established. In detail, the support device 10 judges that a special condition is established when either of the following conditions C1 and C2 is established. Condition C1: A predetermined determination time Td has elapsed from the time when it is detected that the driver is dozing off (time t1 shown in FIG. 2) while the driver remains dozing off. Condition C2: A determination time Td has elapsed from the time when it is detected that the driver has erroneously operated the accelerator pedal 32a while the accelerator pedal 32a is still being erroneously operated.

[0040] The support device 10 makes it easier for the light collision condition to be satisfied as the time that has passed since the specific condition was satisfied and the driver remains in the specific state (hereinafter referred to as the "elapsed time") becomes longer. As an example, the support device 10 makes the light collision threshold value GBth and the integral threshold value Vth smaller as the elapsed time becomes longer.

[0041] The longer the elapsed time, the higher the possibility that the driver is in an unusual state. Furthermore, the more likely it is that the minor collision condition will be established, the higher the possibility that the first braking control will be erroneously executed. Even if the first braking control is erroneously executed when the driver is in a specific state, the driver is less likely to feel bothered by it for the following reasons.

[0042] When the driver erroneously operates the accelerator pedal 32a, the vehicle VA accelerates against the driver's will, and therefore the driver is unlikely to feel bothered even if the first braking control is executed. If the driver is dozing off, there is a possibility that the driver will be woken up by the change in behavior of the vehicle VA due to the first braking control, and the driver is unlikely to feel bothered by it.

[0043] According to the present support device 10, the more likely it is that the driver is in a specific state, the more likely it is that the minor collision condition will be established, and therefore the more likely it is that the first braking control will be executed even in the event of a minor collision in which deployment control is not executed (collision of the vehicle VA with a guardrail, curb, etc.). This increases the possibility of reducing secondary damage after the occurrence of a minor collision. Furthermore, as the minor collision condition becomes more likely to be established, the more likely it is that the first braking control will be executed erroneously. However, even if the first braking control is executed erroneously, the driver is less likely to feel that the first braking control is bothersome, since the driver is more likely to be in a specific state.

[0044] (Example of operation) An example of the operation of the support device 10 will be described with reference to FIG. <Time t1> At time t1, the support device 10 detects that the driver is dozing based on the driver's seat image and issues a warning to the driver. In detail, the support device 10 turns on the dozing indicator light of the display 52, turns on the hazard lamps 54, and causes the speaker 56 to emit an alarm.

[0045] <Time t2> Time t2 is the time when the determination time Td for "the driver remains dozing" has elapsed from time t1. At time t2, the assistance device 10 determines that the above condition C1 is satisfied, and thus determines that the special condition is satisfied.

[0046] Meanwhile, in normal times when the special condition is not satisfied, the support device 10 sets the light collision threshold Gbth to "GBth1" and the integral threshold Vth to "Vth1." At time t2, the support device 10 sets the light collision threshold GBth to "GBth2" and the integral threshold Vth to "Vth2." "GBth2" is a smaller value than "GBth1," and "Vth2" is a smaller value than "Vth1."

[0047] <Time t3> At time t3 when a certain time Tc has elapsed from time t2 when the specific condition is satisfied, the support device 10 sets the light collision threshold Gbth to "GBth3" and the integral threshold Vth to "Vth3." "GBth3" is a value smaller than "GBth2," and "Vth3" is a value smaller than "Vth2."

[0048] <Time t4> At time t4, the vehicle VA collides with the guard rail GR, the acceleration G becomes equal to or greater than the light collision threshold GBth3, and the acceleration integral value V becomes equal to or greater than the integral threshold Vth3. At time t4, the assistance device 10 determines that the light collision condition is met, and executes the first braking control.

[0049] For example, assume that the acceleration G at time t4 is equal to or greater than GBth3 and less than GBth2, and the integral value at time t4 is equal to or greater than Vth3 and less than Vth2. The assistance device 10 makes it easier for the minor collision condition to be satisfied as the elapsed time increases, and is thereby able to determine that the collision of the vehicle VA with the guardrail GR at time t4 is a minor collision and to execute the first braking control.

[0050] (Specific operation) <Drowsy driving detection routine> The CPU of the DSECU 20 (hereinafter, unless otherwise specified, this refers to the CPU of the DSECU 20) executes a dozing determination routine shown in the flowchart of FIG. 3 every time a predetermined time has elapsed.

[0051] Therefore, at a predetermined timing, the CPU starts the process from step 300 in FIG. 3, proceeds to step 305, and determines whether the value of the dozing flag XC1 is "0" or not.

[0052] The value of the drowsy driver flag XC1 is set to "1" when the above condition C1 is satisfied (see step 315), and is set to "0" when it is determined that the driver has returned to a normal state from a drowsy driver state (see step 330). Furthermore, in an initial routine executed by the CPU when an ignition switch (not shown) is changed from the OFF position to the ON position, the value of the drowsy driver flag XC1 is set to "0."

[0053] If the value of the drowsy state flag XC1 is "0", the CPU judges "Yes" in step 305 and proceeds to step 310. In step 310, the CPU judges, based on the driver's seat image, whether the drowsy state has continued for the judgment time Td or more (i.e., whether the above condition C1 is satisfied).

[0054] In detail, the CPU detects the drowsy state when the driver's eyes are closed for a predetermined time or more. Then, the CPU judges whether the determination time Td has elapsed while the driver remains in the drowsy state from the time of the detection. When the CPU detects the drowsy state, it starts turning on the drowsy indicator light, turning on the hazard lamp 54, and emitting the alarm sound.

[0055] If the drowsy state has not continued for the determination time Td or longer, the CPU makes a "No" determination in step 310, proceeds to step 395, and temporarily ends this routine.

[0056] If the dozing state continues for the determination time Td or more, the CPU determines "Yes" in step 310 and proceeds to step 315. In step 315, the CPU sets the value of the dozing flag XC1 to "1" and sets the value of the dozing timer TMC1 to "0." After that, the CPU proceeds to step 395 and temporarily ends this routine.

[0057] The dozing timer TMC1 is a timer that counts the time that has elapsed since the above condition C1 was met.

[0058] On the other hand, if the value of the drowsy flag XC1 is "1" when the CPU proceeds to step 305, the CPU determines "No" in step 305 and proceeds to step 320. In step 320, the CPU determines whether the driver's eyes are open (hereinafter referred to as "eyes open state") has continued for a predetermined period of time or more.

[0059] If the eye-open state has not continued for the predetermined time or longer, the CPU determines "No" in step 320 and proceeds to step 325. In step 325, the CPU adds "1" to the value of the dozing timer TMC1, proceeds to step 395, and ends this routine.

[0060] If the eye-open state continues for a predetermined time or longer, the CPU determines "Yes" in step 320 and proceeds to step 330. In step 330, the CPU sets the value of the dozing flag XC1 to "0" and sets the value of the dozing timer TMC1 to "0." After that, the CPU proceeds to step 395 and temporarily ends this routine.

[0061] <Misoperation detection routine> The CPU executes an error operation determination routine shown in the flowchart of FIG. 4 every time a predetermined time period has elapsed.

[0062] Therefore, at a predetermined timing, the CPU starts the process from step 400 in FIG. 4, proceeds to step 405, and determines whether the value of the error flag XC2 is "0" or not.

[0063] The value of the erroneous operation flag XC2 is set to "1" when the above condition C2 is satisfied (see step 415), and is set to "0" when it is determined that the accelerator pedal 32a is no longer erroneously operated (see step 430). Furthermore, in the above initial routine, the value of the erroneous operation flag XC2 is set to "0."

[0064] If the value of the erroneous operation flag XC2 is "0", the CPU determines "Yes" in step 405 and proceeds to step 410. In step 410, the CPU determines, based on the accelerator operation amount AP, whether or not the erroneous operation of the accelerator pedal 32a has continued for a determination time period Td or longer.

[0065] In detail, the CPU detects that the accelerator pedal 32a has been erroneously operated if the accelerator operation amount AP becomes equal to or greater than a predetermined first operation amount threshold APth1 within a predetermined time from when the accelerator operation speed APV becomes equal to or greater than a predetermined speed threshold APVth. The CPU then determines whether or not a determination time Td has elapsed from the time when the erroneous operation of the accelerator pedal 32a was detected without the accelerator operation amount AP becoming equal to or less than a "predetermined second operation amount threshold APth2 that is set to a value smaller than the first operation amount threshold APth1."

[0066] If the erroneous operation of the accelerator pedal 32a has not continued for the determination time Td or longer, the CPU makes a "No" determination in step 410, proceeds to step 495, and temporarily ends this routine.

[0067] On the other hand, if the erroneous operation of the accelerator pedal 32a continues for the determination time Td or longer, the CPU determines "Yes" in step 410 and proceeds to step 415. In step 415, the CPU sets the value of the erroneous operation flag XC2 to "1" and sets the value of the erroneous operation timer TMC2 to "0." After that, the CPU proceeds to step 495 and temporarily ends this routine.

[0068] The error operation timer TMC2 is a timer that counts the time that has elapsed since the above condition C2 was satisfied.

[0069] If the value of the erroneous operation flag XC2 is "1" when the CPU proceeds to step 405, the CPU determines "No" in step 405 and proceeds to step 420. In step 420, the CPU determines whether the accelerator operation amount AP is equal to or less than the second operation amount threshold APth2.

[0070] If the accelerator operation amount AP is greater than the second operation amount threshold APth2, the CPU determines that the erroneous operation of the accelerator pedal 32a is still continuing. In this case, the CPU determines "No" in step 420 and proceeds to step 425. In step 425, the CPU adds "1" to the value of the erroneous operation timer TMC2, proceeds to step 495, and temporarily ends this routine.

[0071] If the accelerator operation amount AP is equal to or less than the second operation amount threshold APth2, the CPU determines that the erroneous operation of the accelerator pedal 32a has ended. In this case, the CPU determines "Yes" in step 420 and proceeds to step 430. In step 430, the CPU sets the value of the erroneous operation flag XC2 to "0" and sets the value of the erroneous operation timer TMC2 to "0". After that, the CPU proceeds to step 495 and temporarily ends this routine.

[0072] <Collision detection routine> The CPU executes a collision determination routine shown in the flowchart of FIG. 5 every time a predetermined time elapses.

[0073] Therefore, at a predetermined timing, the CPU starts the process from step 500 in FIG. 5, proceeds to step 505, and determines whether the value of the collision flag Xc is "0" or not.

[0074] The value of the collision flag Xc is set to "1" when a collision occurs (see step 560), and is set to "0" when a termination condition for the second braking control, which will be described later, is satisfied (see step 825 shown in FIG. 8). Note that in the above initial routine, the value of the collision flag Xc is set to "0."

[0075] If the value of the collision flag Xc is "0", the CPU determines "Yes" in step 505 and executes steps 510 to 520 in order.

[0076] Step 510: The CPU determines the acceleration G based on the detection signal from the acceleration sensor 24. Step 515: The CPU obtains an acceleration integral value V by integrating the acceleration G. This integration process is described in paragraphs 0044 to 0047 of JP 2021-112983 A, and will be briefly explained below.

[0077] The CPU obtains, as an acceleration integral value V, an integral value of the acceleration G from the start timing to the end timing as follows.

[0078] The start timing is the timing when the section integral value of the acceleration G becomes equal to or greater than a predetermined first integral threshold value. The section integral value is the integral value of the acceleration G within a predetermined section width.

[0079] The end timing is the timing when a first set time has elapsed since the interval integral value became equal to or less than a second integral threshold, or the timing when a second set time has elapsed since the start timing, whichever comes first. The second set time is set to be longer than the first set time.

[0080] Step 520: The CPU determines whether or not the values ​​of the dozing flag XC1 and the erroneous operation flag XC2 are both "0".

[0081] If the values ​​of the dozing flag XC1 and the erroneous operation flag XC2 are both "0", the CPU judges "Yes" in step 520 and executes steps 525 to 535 in order.

[0082] Step 525: The CPU sets the light collision threshold GBth to "GBth1". Step 530: The CPU sets the integral threshold Vth to "Vth1." Step 535: The CPU determines whether the magnitude of the acceleration G is equal to or greater than the light collision threshold GBth and less than the collision threshold GAth.

[0083] If the magnitude of the acceleration G is less than the light collision threshold GBth or equal to or greater than the collision threshold GAth, the CPU determines "No" in step 535 and proceeds to step 540. In step 540, the CPU determines whether the magnitude of the acceleration G is equal to or greater than the collision threshold GAth.

[0084] If the magnitude of the acceleration G is less than the collision threshold value GAth, the CPU makes a "No" determination in step 540, proceeds to step 595, and temporarily ends this routine.

[0085] When the CPU proceeds to step 535 , if the magnitude of the acceleration G is equal to or greater than the light collision threshold GBth and less than the collision threshold GAth, the CPU determines “Yes” in step 535 and proceeds to step 545 .

[0086] In step 545, the CPU determines whether the magnitude of the acceleration integral value V is equal to or greater than an integral threshold value Vth.

[0087] If the magnitude of the acceleration integral value V is less than the integral threshold value Vth, the CPU determines that a minor collision has not occurred. In this case, the CPU determines "No" in step 545, proceeds to step 595, and temporarily ends this routine.

[0088] If the magnitude of the acceleration integral value V is equal to or greater than the integral threshold value Vth, the CPU determines that a minor collision has occurred. In this case, the CPU determines "Yes" in step 545 and proceeds to step 550. In step 550, the CPU sets the value of the minor collision flag XLc to "1", proceeds to step 595, and temporarily ends this routine.

[0089] If the magnitude of the acceleration G is equal to or greater than the collision threshold value GAth when the CPU proceeds to step 540, the CPU determines that a collision has occurred. In this case, the CPU determines "Yes" in step 540 and executes steps 560 and 565 in this order.

[0090] Step 560: The CPU sets the value of the collision flag Xc to “1”. Step 565 : The CPU sends an ignition signal to the inflator 60 . As described above, the inflator 60 deploys the airbag 62 upon receiving an ignition signal. Thereafter, the CPU proceeds to step 595 and ends this routine.

[0091] If at least one of the values ​​of the dozing flag XC1 and the erroneous operation flag XC2 is "1" when the CPU proceeds to step 520, the CPU judges "No" in step 520 and proceeds to step 570 to execute a threshold setting subroutine. After that, the CPU proceeds to the processing of step 535 and subsequent steps.

[0092] <Threshold setting subroutine> 5, the CPU starts the process from step 600 shown in Fig. 6, and proceeds to step 605. In step 605, the CPU determines whether or not the values ​​of the dozing flag XC1 and the erroneous operation flag XC2 are both "1".

[0093] If the value of at least one of the dozing flag XC1 and the erroneous operation flag XC2 is "0", the CPU judges "No" in step 605 and proceeds to step 610. If the value of the dozing flag XC1 is "1" in step 610, the CPU judges "Yes" in step 610 and executes steps 615 and 620 in this order.

[0094] Step 615: The CPU sets the value of the elapsed time timer TM to the value of the doze timer TMC1. Step 620: The CPU determines whether the value of the elapsed time timer TM is equal to or less than a predetermined fixed time threshold Tcth. The fixed time threshold Tcth is set so that the value of the elapsed time timer TM reaches the fixed time threshold Tcth when the elapsed time reaches the fixed time Tc.

[0095] If the value of the elapsed time timer TM is equal to or less than the certain time threshold Tcth, the CPU determines "Yes" in step 620 and executes steps 625 and 630 in this order. Step 625: The CPU sets the light collision threshold GBth to "GBth2." Step 630: The CPU sets the integral threshold Vth to "Vth2." Thereafter, the CPU proceeds to step 695 to temporarily end this routine, and then proceeds to step 535 shown in FIG.

[0096] When the CPU proceeds to step 620, if the value of the elapsed time timer TM is greater than the certain time threshold Tcth, the CPU determines "No" in step 620 and executes steps 635 and 640 in this order.

[0097] Step 635: The CPU sets the light collision threshold GBth to “GBth3”. Step 640: The CPU sets the integral threshold Vth to "Vth3." Thereafter, the CPU proceeds to step 695 to temporarily end this routine, and then proceeds to step 535 shown in FIG.

[0098] If the value of the dozing flag XC1 is "0" when the CPU proceeds to step 610, the value of the error flag XC2 is "1" because the determination in step 520 shown in FIG. 5 is "No." In this case, the CPU determines "No" in step 610 and proceeds to step 645. In step 645, the CPU sets the value of the elapsed time timer TM to the value of the error timer TMC2. Thereafter, the CPU proceeds to processing from step 620 onwards.

[0099] When the CPU proceeds to step 605, if the values ​​of the dozing flag XC1 and the erroneous operation flag XC2 are both “1”, the CPU judges “Yes” in step 605 and proceeds to step 650.

[0100] In step 650, the CPU determines whether the value of the doze timer TMC1 is equal to or greater than the value of the error timer TMC2.

[0101] If the value of the doze timer TMC1 is equal to or greater than the value of the error timer TMC2, the CPU determines "Yes" in step 650, and sets the value of the elapsed time timer TM to the value of the doze timer TMC1 in step 615. After that, the CPU proceeds to the process of step 620 and subsequent steps.

[0102] If the value of the doze timer TMC1 is less than the value of the error timer TMC2, the CPU determines "No" in step 650, and sets the value of the elapsed time timer TM to the value of the error timer TMC2 in step 645. After that, the CPU proceeds to the process of step 620 and subsequent steps.

[0103] <First Brake Control Routine> The CPU executes a first braking control routine shown in the flowchart of FIG. 7 every time a predetermined time elapses.

[0104] Therefore, at a predetermined timing, the CPU starts the process from step 700 in FIG. 7, and proceeds to step 705 to determine whether the value of the minor collision flag XLc is "1".

[0105] If the value of the minor collision flag XLc is "0", the CPU makes a "No" determination in step 705, proceeds to step 795, and temporarily ends this routine.

[0106] If the value of the minor collision flag XLc is “1”, the CPU determines “Yes” in step 705 and proceeds to step 710 .

[0107] In step 710, the CPU determines whether or not a condition for ending the first braking control is met. More specifically, the CPU determines that the above-mentioned termination condition is met when any one of the following conditions D1 to D3 is met. Condition D1: The driver recovers from a drowsy state and the value of the drowsy flag XC1 changes from "1" to "0." Condition D2: The erroneous operation of the accelerator pedal 32a ends and the value of the erroneous operation flag XC2 changes from "1" to "0." Condition D3: The vehicle speed Vs becomes "0 km / h."

[0108] If none of the above conditions D1 to D3 is met, the CPU determines "No" in step 710 and executes steps 715 and 720 in this order. Step 715: The CPU sets the target acceleration Gtgt to a predetermined first deceleration Gd1 (<0). Step 720: A deceleration command including the target acceleration Gtgt is transmitted to the drive ECU 30 and the brake ECU 40. When the drive ECU 30 and the brake ECU 40 receive a deceleration command, they respectively control the drive source actuator 34 and the brake actuator 44 so that the longitudinal component Gx of the vehicle acceleration G coincides with the first deceleration Gd1. Thereafter, the CPU proceeds to step 795 and ends this routine.

[0109] If any one of the above conditions D1 to D3 is satisfied, the CPU determines "Yes" in step 710 and proceeds to step 725. In step 725, the CPU sets the value of the minor collision flag XLc to "0." As a result, if any one of the above conditions D1 to D3 is satisfied, the CPU will no longer transmit a deceleration command, and the first braking control will end. Thereafter, the CPU proceeds to step 795 and ends this routine.

[0110] <Second Brake Control Routine> The CPU executes a second braking control routine shown in the flowchart of FIG. 8 every time a predetermined time elapses.

[0111] Therefore, at a predetermined timing, the CPU starts the process from step 800 in FIG. 8, and proceeds to step 805 to determine whether the value of the collision flag Xc is "1".

[0112] If the value of the collision flag Xc is "0", the CPU makes a "No" determination in step 805, proceeds to step 895, and temporarily ends this routine.

[0113] If the value of the collision flag Xc is "1", the CPU determines "Yes" in step 805 and proceeds to step 810. In step 810, the CPU determines whether or not an end condition for the second braking control is met. More specifically, if the above condition D3 is satisfied, the CPU determines that the above termination condition is satisfied.

[0114] If the above condition D3 is not satisfied, the CPU determines "No" in step 810 and executes steps 815 and 820 in this order. Step 815: The CPU sets the target acceleration Gtgt to a predetermined second deceleration Gd2 (<0). Note that the second deceleration Gd2 is set to a negative value smaller than the first deceleration Gd1. Step 820: A deceleration command including the target acceleration Gtgt is transmitted to the drive ECU 30 and the brake ECU 40. Thereafter, the CPU proceeds to step 895 and ends this routine.

[0115] When the above condition D3 is satisfied, the CPU determines "Yes" in step 810 and proceeds to step 825. In step 825, the CPU sets the value of the collision flag Xc to "0." As a result, when the above condition D3 is satisfied, the CPU stops transmitting the deceleration command and the second braking control ends. Thereafter, the CPU proceeds to step 795 and ends this routine.

[0116] As a result, when a minor collision occurs, the value of the minor collision flag XLc is set to "1" and the first braking control is executed. On the other hand, when a collision occurs, the value of the collision flag Xc is set to "1" and the deployment control (airbag deployment and second braking control) is executed. When the driver is in a peculiar state, the values ​​of the thresholds (minor collision threshold GBth and integral threshold Vth) used to determine a minor collision become smaller as the time that has elapsed since the driver entered the peculiar state becomes longer (in other words, the above thresholds are set so that the minor collision condition becomes more likely to be established as the time that has elapsed becomes longer).

[0117] This increases the likelihood that the first braking control will be executed when the vehicle collides with a guardrail, a curb, etc., and reduces the likelihood that the first braking control will be felt as a nuisance even if the first braking control is executed by mistake.

[0118] The present invention is not limited to the above-described embodiment, and various modifications of the present invention can be adopted.

[0119] (First Modification) The driving support device 10 according to this modification executes driving force suppression control instead of the first braking control when a minor collision occurs. The driving force suppression control is a control that suppresses the driving force generated by the driving source 34a to a driving force smaller than the "required driving force, which is a driving force based on the accelerator operation amount AP." The driving force suppression control may be a control that causes the driving source 34a to generate a threshold driving force when the required driving force is equal to or greater than a threshold driving force (i.e., a control that limits the driving force generated by the driving source 34a so as not to exceed the threshold driving force).

[0120] The first braking control and the driving force suppression control are controls for the braking force and driving force of the vehicle VA, and therefore may be referred to as "braking / driving force control".

[0121] It should be noted that the assistance device 10 may execute the driving force suppression control instead of the second braking control when a collision occurs.

[0122] (Second Modification) The support device 10 according to this modified example determines that the minor collision condition is met when the first condition is met even if the second condition is not met. However, determining that the minor collision condition is satisfied when both the first and second conditions are satisfied reduces the possibility of erroneously determining that a minor collision has occurred when the vehicle VA is traveling on a rough road, because the magnitude of the acceleration integral value V when a minor collision actually occurs tends to be larger than the magnitude of the acceleration integral value V when the vehicle VA is traveling on a rough road.

[0123] (Third Modification) In the above embodiment, the light collision threshold GBth and the integral threshold Vth are made smaller than normal when the special condition is satisfied (time t2 shown in FIG. 2), and are further made smaller when a certain time Tc has elapsed from the time when the special condition is satisfied (time t3 shown in FIG. 3). In this modified example, the light collision threshold GBth and the integral threshold Vth may be made smaller by a predetermined value each time a certain time Tc has elapsed from the time when the special condition is satisfied.

[0124] (Fourth Modification) In the above embodiment, the light collision condition is made easier to be satisfied by decreasing the light collision threshold value GBth and the integral threshold value Vth as the elapsed time increases, but the present invention is not limited to the above example as long as the light collision condition is made easier to be satisfied as the elapsed time increases. For example, the light collision threshold value GBth or the integral threshold value Vth may be made smaller as the elapsed time increases.

[0125] (Fifth Modification) The driving support device 10 according to this modification may determine that the light collision condition is satisfied when a first multiplication value obtained by multiplying the acceleration G by the first weighting factor α is equal to or greater than a light collision threshold GBth and a second multiplication value obtained by multiplying the acceleration integral value V by the second weighting factor β is equal to or greater than an integral threshold Vth. In this case, the light collision condition may be made more likely to be satisfied by decreasing at least one of the first weighting factor α and the second weighting factor β as the elapsed time increases.

[0126] (Sixth Modification) The driving assistance device 10 according to this modified example only deploys the airbag 62 without executing the second braking control when a collision occurs.

[0127] (Seventh Modification) The driving assistance device 10 can be mounted on vehicles such as an engine vehicle, a hybrid vehicle (HEV: Hybrid Electric Vehicle), a plug-in hybrid electric vehicle (PHEV: Plug-in Hybrid Electric Vehicle), a fuel cell electric vehicle (FCEV: Fuel Cell Electric Vehicle), and an electric vehicle (BEV: Battery Electric Vehicle). [Explanation of symbols]

[0128] 10...driving assistance device, 20...driving assistance ECU, 30...driving ECU, 32a...accelerator pedal, 34...driving source actuator, 34a...driving source, 40...brake ECU, 44...brake actuator, 44a...braking device, 60...inflator, 62...airbag.

Claims

1. an acceleration sensor configured to measure an acceleration acting on a body of the vehicle; A control unit configured to execute a damage mitigation control for mitigating damage caused by a collision when the vehicle collides; Equipped with The control unit When a collision index value obtained based on the acceleration and indicating a degree of a collision of the vehicle satisfies a predetermined collision condition, a deployment control including at least a control for deploying an airbag of the vehicle is executed as the damage mitigation control, When the collision index value does not satisfy the collision condition but satisfies a predetermined minor collision condition that is established when the collision is less severe than the collision condition, a driving force of the vehicle is made smaller than a driving force requested by a driver of the vehicle, or a braking / driving force control that applies a braking force to the vehicle is executed as the damage reduction control, The longer the elapsed time that indicates the time that has elapsed since the time when the specific condition that the driver is in a specific state not performing normal driving is established, the more likely the minor collision condition is established. It was configured as follows: Driving assistance device.

2. The driving assistance device according to claim 1, The control unit If the collision index value is equal to or greater than a predetermined collision threshold, the collision condition is satisfied; When at least a first condition is satisfied that the collision index value is equal to or greater than a predetermined light collision threshold value set to a value smaller than the collision threshold value and is less than the collision threshold value, the light collision condition is satisfied; The longer the elapsed time is, the smaller the light collision threshold is set, thereby making it easier for the light collision condition to be satisfied. It was configured as follows: Driving assistance device.

3. The driving assistance device according to claim 2, The control unit is configured to establish the light collision condition when the first condition is established and a second condition is established in which a magnitude of an integral value of the collision index value is equal to or greater than a predetermined integral threshold value. Driving assistance device.

4. The driving support device according to claim 3, the control unit is configured to make the light collision condition more likely to be satisfied by decreasing the light collision threshold value and the integral threshold value as the elapsed time becomes longer. Driving assistance device.

5. The driving assistance device according to claim 1, The control unit is configured to establish the special condition when the driver is in an erroneous operation state in which the driver erroneously operates an acceleration operation element operated to accelerate the vehicle, or when the driver is in a drowsy state. Driving assistance device.

Citation Information

Patent Citations

  • Vehicle-mounted alarm apparatus

    JP2008097446A

  • Vehicle collision safety device

    JP2013082298A

  • Driving support apparatus

    JP2021112982A

  • Driving support apparatus

    JP2021112983A