Movement path control method for a motor vehicle
The vehicle path control method aligns the actual path with the driver's intended path by adjusting braking in response to deviations, enhancing safety and control during autonomous braking.
Patent Information
- Application Number
- DE102009006299
- Authority / Receiving Office
- DE · DE
- Patent Type
- Patents
- Current Assignee / Owner
- Priority Date
- 2008-01-30
- Filing Date
- 2009-01-27
- Publication Date
- 2024-11-28
- Estimated Expiration
- 2029-01-27
AI Technical Summary
Existing collision preparation systems cause the actual vehicle path to deviate from the driver's intended path during autonomous braking events.
A motor vehicle path control method that monitors and adjusts braking to align the actual path with the driver's intended path by evaluating inputs from the vehicle and collision preparation system, implementing rapid sequences of brake adjustments to match yaw rates.
Maintains the vehicle on the driver's intended path during autonomous braking events, ensuring safety and control by minimizing deviations.
Smart Images

Figure 00000000_0000_ABST
Abstract
Description
TECHNICAL FIELD
[0001] The present invention relates to collision preparation systems in which autonomous braking may be provided, and in particular to a trajectory control method for a motor vehicle.
[0002] A control method according to the preamble of claim 1 is known, for example, from DE 102 44 557 A1.
[0003] Furthermore, it is known from DE 101 21 386 C1 to detect any understeering or oversteering of a vehicle based on a comparison between the desired vehicle trajectory and the actual vehicle trajectory. In this case, there is a certain risk of an accident, which is why a reversible occupant protection device such as an airbag, a belt tensioner, or a movable headrest is activated for safety reasons.
[0004] Further state of the art can be found in DE 103 56 501 A1. BACKGROUND OF THE INVENTION
[0005] Electronic stability control (ESC) is the generic term for systems designed to enhance vehicle handling, particularly at the limits where the driver could lose control. See, for example, the Society of Automotive Engineers (SAE) document on "Automotive Stability Enhancement Systems," publication J2564 (12 / 2000, 6 / 2004). ESC compares the driver's intended steering direction and braking inputs with the vehicle's response via lateral acceleration, rotation (yaw), and individual wheel speeds, and then applies brakes to individual front or rear wheels and / or reduces excessive engine power as needed to assist with correct understeer (ploughing) or oversteer (fishtailing).The ESC also integrates traction control at all speeds, which detects drive wheel slip during acceleration and individually brakes the wheel(s) experiencing slippage and / or reduces excessive engine power until control is regained. The ESC cannot overcome the physical limits of the vehicle. Of course, if a driver pushes the vehicle's chassis and ESC too far, the ESC cannot prevent an accident. It is a tool designed to help the driver maintain control. The ESC combines anti-lock braking, traction control, and yaw control (yaw is a rotation around the vertical axis).
[0006] ESC systems use multiple sensors to determine the desired state of the vehicle based on the driver's intention (driver demand). Other sensors indicate the actual state of the vehicle (vehicle response). The ESC control algorithm compares both states and decides, if necessary, to adjust the vehicle's dynamic state. The sensors used for ESC must transmit data at all times to detect potential errors as quickly as possible. They must be resilient to possible forms of disturbance (rain, potholes in the road, and the like).The most important sensors are: 1) steering wheel sensor, used to determine the angle desired by the driver and often based on anisotropic magnetoresistive (AMR) elements; 2) lateral acceleration sensor, used to measure the lateral acceleration of the vehicle; 3) yaw sensor, used to measure the yaw angle (rotation) of the vehicle, which can be compared by the ESC with the data from the steering wheel sensor to make a regulatory intervention; and 4) wheel speed sensors, used to measure the wheel speeds.
[0007] The ESC, for example, uses a hydraulic modulator to ensure that each wheel receives the correct braking force. A similar modulator is used in anti-lock braking systems (ABS). The ABS only needs to reduce pressure during braking. The ESC must also increase the braking pressure in certain situations.
[0008] The heart of the ESC system is the electronic control unit (ECU) or electronic control module (ECM), i.e., the automotive controller or microprocessor. Various control technologies are embedded in the ECU, with the same ECU often being used for different systems (ABS, traction control, climate control, etc.). The desired vehicle state is determined based on the steering wheel angle, its gradient, and the wheel speed. At the same time, the yaw sensor measures the actual state. The controller calculates the required braking or acceleration force for each wheel and controls the actuation of, for example, the valves of a hydraulic brake modulator.
[0009] Motor vehicles employing electronic stability control systems require a means for determining the driver's desired vehicle behavior (i.e., the intended vehicle path or trajectory). In the General Motors (GM) StabiliTrak system, this means is provided by the driver command interpreter described in U.S. Patent No. 5,941,919, issued August 24, 1999, to the assignee hereof.
[0010] In Fig. 1 shows the exemplary control structure described in US patent US 5,941,919 A. The controller 10 includes a command interpreter 12 that receives various system inputs 14 from various vehicle sensors. The command interpreter 12 develops desired yaw rate commands in response to the various system inputs and a data structure 16 stored in a non-volatile memory of the controller 10. The data structure 16 has a data subset 18 corresponding to vehicle operation in a linear mode and a data subset 20 corresponding to vehicle operation in a non-linear mode.
[0011] When vehicle operation is in a linear mode, command interpreter 12, using data structure subset 18, provides commands to a control block 22 designed to maintain a linear vehicle response. For example, when the controller according to this patent is used to control wheel brakes to affect vehicle yaw control, the commands provided by block 12 do not modify wheel brake operation when the vehicle is in the linear mode. When the controller according to this patent is used to control a variable-force vehicle suspension system, suspension control is provided to maintain the current drive conditions, causing no change in understeer or oversteer.
[0012] When vehicle operation is in the nonlinear regime, command interpreter 12, using data structure subset 20, provides commands to control block 22 that linearly control the yaw rate in response to the vehicle steering wheel input. Block 22 uses the command generated in block 12 to control one or more vehicle chassis systems, such as controllable suspension actuators represented by block 24 and / or brakes represented by block 26, to bring the actual vehicle yaw into a linear relationship with the vehicle steering wheel angle.
[0013] This control therefore keeps the vehicle's yaw response with respect to the steering wheel input in the linear range even when the vehicle is operated in its non-linear behavior range.
[0014] Collision preparation systems are known in the art, as indicated, for example, by: US patent US 7 280 902 B2, which discloses a motor vehicle deceleration control device; US patent US 7 035 735 B2, which discloses a method and apparatus for automatically initiating deceleration of a motor vehicle; and US patent publication US 2004 / 0254729 A1, which discloses a pre-collision assessment of the severity of a potential collision for motor vehicles.
[0015] Of particular interest with regard to the present invention is US patent US 6 084 508 A, issued on July 4, 2000. US patent US 6 084 508 A discloses a collision preparation system that provides for automatic braking in certain situations.The method and arrangement for emergency braking of a vehicle comprise a detection system in the vehicle which detects obstacles which are in the direction of movement of the vehicle or in their vicinity and generates corresponding data, sensors in the vehicle which generate data which represent characteristic parameters of the state of the vehicle, and an evaluation unit which determines setpoints for controlling the movement of the vehicle from the data on the obstacles and from the parameters of the state of the vehicle and which triggers autonomous emergency braking in order to quickly decelerate the vehicle only when it is determined that an imminent collision of the vehicle with an obstacle can no longer be avoided by any intervention in the vehicle by steering or braking.
[0016] It is problematic when a self-braking event due to the actuation of a collision preparation system (CPS) results in the actual motor vehicle trajectory during the self-braking event deviating from the motor vehicle trajectory intended by the driver.
[0017] Therefore, what is needed in the art is a motor vehicle trajectory controller that monitors the actual motor vehicle trajectory relative to the driver's intended motor vehicle trajectory during a self-braking event, wherein the motor vehicle trajectory controller adjusts braking to return the motor vehicle trajectory to the driver's intended motor vehicle trajectory in the event that a deviation from the driver's intended motor vehicle trajectory occurs.
[0018] It is an object of the present invention to provide a motor vehicle motion path control that keeps the motor vehicle aligned in the direction intended by the driver during a self-braking event. SUMMARY OF THE INVENTION
[0019] This object is achieved by a movement path control method having the feature of claim 1.
[0020] The present invention is a motor vehicle trajectory controller that monitors the actual motor vehicle trajectory relative to the driver's intended motor vehicle trajectory during a CPS-initiated autonomous braking event, wherein the motor vehicle trajectory controller adjusts braking to return the motor vehicle trajectory to the driver's intended motor vehicle trajectory in the event that a deviation from the driver's intended motor vehicle trajectory occurs.
[0021] To this end, inputs from the motor vehicle and from a CPS are evaluated in an electronic controller in accordance with predetermined programming, whereby braking is adjusted to align the actual motor vehicle path of travel with the path of travel intended by the driver. For example, in a self-braking situation in which the motor vehicle turn radius becomes larger than the turn radius intended by the driver (ieIf the actual yaw rate does not match the intended yaw rate due to understeer, for example, when inertial forces exceed the adhesion of the tires to the road surface, the vehicle trajectory control according to the present invention would adjust the brakes through a rapid sequence of brake reduction commands until the actual yaw rate and the intended yaw rate match each other. Thereafter, braking would be permitted to increase up to the CPS braking request, depending on the match between the actual vehicle trajectory and the driver's intended vehicle trajectory. Preferably, the brake adjustment provided by the present invention is not executed in the event that the driver has requested braking that exceeds the braking requested by the CPS. BRIEF DESCRIPTION OF THE DRAWINGS Fig. 1 is a partial block diagram of a prior art electronic stability control system. Fig. Figure 2 is a block diagram of an algorithm for implementing programming according to the present invention. Fig. 3A is a schematic illustration of a motor vehicle equipped with a CPS and an exemplary motor vehicle motion path controller according to the present invention. Fig. 3B is a block diagram of an apparatus for carrying out the present invention. Fig. Figure 4 is a diagrammatic illustration of the operation of the present invention during self-braking events. DESCRIPTION OF THE PREFERRED EMBODIMENT
[0022] Now reference is made to the drawing in which the Fig. 2 to 4 illustrate an example of a motor vehicle trajectory control implemented during a self-braking event that makes adjustments to braking as needed to return the actual motor vehicle trajectory to the driver's intended trajectory.
[0023] Fig. Figure 2 is an example of a programming algorithm 100 for implementing the motor vehicle motion path control according to the present invention, which is incorporated in an electronic controller included in the Fig. 3A and 3B at 224 as an example.
[0024] Beginning at block 102, the program is initialized. In decision block 104, a query is made as to whether a collision preparation system (CPS) has been activated, so that autonomous braking has been implemented. If the answer to the query is no, the program returns and waits. However, if the answer to the query is yes, the program proceeds to block 106, where a determination is made as to whether the driver of the motor vehicle has requested braking that exceeds that requested by the CPS (in practice, whether the driver has requested braking that exceeds a predetermined small area in its vicinity). If the answer to the query is yes, the program returns and waits.However, if the answer to the query is no, the program proceeds to block 108, where the driver's intended vehicle path is determined, for example, from data received from a steering wheel position sensor. The program then proceeds to block 110, where the actual vehicle path of travel is determined, for example, from the output of the electronic stability control command interpreter (see ). Fig. 3B).
[0025] The program next queries, in decision block 112, whether the actual path of travel of the motor vehicle matches that intended by the driver of the motor vehicle (in practice, this queries whether the difference between them is essentially zero, which includes a predetermined small acceptable difference between them). If the answer to the query is no, in block 114, braking is reduced by a preselected braking decrement (for example, to correct an understeer situation in which reduced braking restores a slip-free condition of the tires with respect to the road surface). The program then returns to block 108. The program continues to execute blocks 108 to 114 in rapid succession (for example, every 20 milliseconds) until the answer to the query in decision block 114 is yes, at which point the program proceeds to decision block 116.
[0026] Decision block 116 queries whether the braking from block 114 is at a level below the braking requested by the CPS by block 106 (in practice, at a level below a predetermined small area in its vicinity). If the answer to the question is yes, the program proceeds to block 118, where the braking is increased by a preselected braking increment. The program then returns to block 108. The program proceeds in rapid succession (e.g., every 20 milliseconds) through blocks 108 to 112 and then, depending on the answer to the question in decision block 112, either to block 114 or to decision block 116 and then to block 118, until the answer to the question in decision block 116 is no, at which point the program proceeds to decision block 104.
[0027] The Fig. 3A and Fig. 3B show an exemplary hardware implementation of the vehicle path control algorithm 100 of Fig. 2.
[0028] Fig. 3A shows a motor vehicle 200 with a braking system 202 including brake actuators 204a, 204b, 204c, and 204d and a braking controller 206. A stability controller 208 operates at least partially like the controller 10 of Fig. 1. The braking system 202 is coupled to a collision preparation system (CPS) 210 via an interface. The CPS 210 may be implemented, for example, as disclosed in US Patent 6,084,508 and may include, for example, a short-range radar 212a, 212b, a long-range radar 214, and an evaluation unit 216. A collision preparation system brake adjustment controller 224 is interfaced to the braking system 202 to adjust braking in accordance with the present invention and receives operating data to perform its function, for example, from the CPS 210 and the stability controller 208.
[0029] Fig. Figure 3B shows the electronic implementation of Fig. 3A, wherein inputs 218 from various sensors and other data sources of the motor vehicle 200 are provided to the stability controller 208. The stability controller 208 includes a command interpreter 220 such as that shown in Fig. 1 at 12. The stability controller 208 uses the command interpreter 220 and the control command block 222 such as that shown in Fig. 1 at 22, to limit the operation of the braking system 202 to the above with reference to Fig. 1 and US patent US 5 941 919 A.
[0030] According to the example of Fig. 3B, the driver braking request, the yaw rate, and / or other data indicative of actual vehicle path information, as well as the steering wheel position and / or other data indicative of driver intended vehicle path information, all available from the command interpreter 220, are provided to the CPS brake adjustment controller 224 via a data line 226, and the activation status of the CPS 210, indicative of the autonomous braking status and the CPS braking request, is further made available to the CPS brake adjustment controller via a data line 228.The CPS brake adjustment controller 224 sends a brake reduction signal to the braking system via the data line 230 if a sensed difference (in practice at least a predetermined small difference) is sensed between the driver's intended vehicle travel path compared to the actual vehicle travel path, wherein the driver braking request preferably does not exceed the CPS braking request, as shown in FIG. Fig. 2 is specified.
[0031] Fig. 4 is a vehicle path representation 300 of movement paths for the motor vehicle 200 of Fig. 3A, which shows a motor vehicle path 302 intended by the driver, in which path there is an obstacle 304 which is detected by the CPS (210 in the Fig. 3A and Fig. 3B) has been detected and in response to which the CPS has activated and implemented autonomous braking, wherein the CPS brake setting controller (224 in the Fig. 3A and Fig. 3B) in the two illustrated alternative scenarios, either an understeer path correction 306 or an oversteer path correction 308 is provided, both of which are successfully managed by the motor vehicle motion path control according to the present invention.
[0032] The following examples illustrate the operation of the present invention. EXAMPLE 1 Motor vehicle traveling in a straight line
[0033] The motor vehicle 200 is traveling on a two-lane road and is approaching a vehicle stationary in its lane. The driver is inattentive. If the collision is unavoidable, the CPS 210 issues a command to apply autonomous braking with maximum deceleration. The vehicle path control algorithm 100 becomes active. Since the vehicle is traveling in a straight line, the yaw rate is approximately 0 degrees / second. The steering wheel angle is approximately zero, indicating that the driver is requesting a yaw rate of 0 degrees / second. Since the actual vehicle path matches the driver's intended vehicle path, the commanded deceleration is not reduced. The actual path is checked every 20 milliseconds and compared to the desired path until the event is resolved. EXAMPLE 2 Motor vehicle located on a highway entrance
[0034] Motor vehicle 200 is moving along a circular highway entrance at a constant speed of 20 m / s. The radius of the entrance is 80 m, which results in a constant lateral acceleration of 5 m / s. 2 In the merging lane of the entrance, there is a driver who, instead of merging onto the highway, has stopped his vehicle. The driver of the moving motor vehicle 200 is inattentive. If the collision is unavoidable, the CPS 210 issues a command to autonomously brake with maximum deceleration. The vehicle path control algorithm 100 becomes active. Initially, the desired yaw rate is slightly more than 7 degrees per second. The actual yaw rate is also slightly more than 7 degrees per second. The actual path is checked every 20 milliseconds and compared to the desired path until the event is over.
[0035] At 220 milliseconds after the onset of the event, the actual path does not match the desired path (understeer) and the vehicle path control algorithm reduces the commanded acceleration to 0.8 g.
[0036] At 240 milliseconds after the start of the event, the actual path still does not match the desired path, so the commanded deceleration is reduced to 0.7 g.
[0037] At 260 milliseconds after the start of the event, the actual path still does not match the desired path, so the commanded deceleration is reduced to 0.65 g.
[0038] At 280 milliseconds after the start of the event, the actual path still does not match the desired path, so the commanded deceleration is reduced to 0.60 g.
[0039] At 300 milliseconds after the start of the event, the actual path still does not match the desired path, so the commanded deceleration is reduced to 0.55 g.
[0040] At 320 milliseconds after the start of the event, the actual displacement is within the calibrated tolerance of the desired displacement, so 0.55 g is commanded.
[0041] At 340 milliseconds after the onset of the event, the actual path is still within the calibrated tolerance of the desired path, so the vehicle path control algorithm allows the commanded deceleration to be increased to 0.6 g.
[0042] At 360 milliseconds after the start of the event, the actual path is still within the calibrated tolerance of the desired path.
[0043] At 380 milliseconds after the onset of the event, the actual path is still within the calibrated tolerance to the desired path and the vehicle path control algorithm allows an increase of the commanded deceleration to 0.65 g.
[0044] At 400 milliseconds after the start of the event, it is determined that the actual path does not match the desired path, so the commanded deceleration is reduced to 0.6 g.
[0045] During the next 300 milliseconds, the actual path remains within the calibrated tolerance to the actual path and the vehicle path control algorithm maintains the deceleration of 0.6 g.
[0046] At 720 milliseconds, the actual path is within the calibrated tolerance to the actual path and the vehicle path control algorithm calculates that the overall acceleration of the vehicle has dropped far enough so that a deceleration of 0.65 g can be commanded.
[0047] At 740 milliseconds after the start of the event, the actual path is still within the calibrated tolerance of the desired path.
[0048] At 760 milliseconds after the start of the event, the actual path is still within the calibrated tolerance of the desired path.
[0049] During the next 360 milliseconds, the actual path is within the calibrated tolerance to the actual path and the vehicle path control algorithm maintains the deceleration at 0.6 g.
[0050] At 1140 milliseconds, the actual path is within the calibrated tolerance to the actual path and the vehicle path control algorithm calculates that the overall acceleration of the vehicle has dropped far enough so that a deceleration of 0.7 g can be commanded.
[0051] The collision with the target vehicle occurs at 1380 milliseconds. EXAMPLE 3Motor vehicle driving in a straight line with evasive maneuver
[0052] Motor vehicle 200 is traveling on a two-lane road and is approaching a vehicle stationary in its lane. The driver is inattentive. If the collision is unavoidable, the CPS 210 issues a command to apply autonomous braking with maximum deceleration. The vehicle path control algorithm 100 becomes active. Since the vehicle is traveling in a straight line, the yaw rate is approximately 0 degrees / second. The steering wheel angle is approximately zero, indicating that the driver is requesting a yaw rate of 0 degrees / second. Since the actual vehicle path matches the driver's intended path, the commanded deceleration is not reduced. The actual path is checked every 20 milliseconds and compared to the desired path until the event is resolved.
[0053] At 580 milliseconds after the start of the event, the driver steers sharply to the right.
[0054] At 600 milliseconds after the start of the event, the actual path is still within the calibrated tolerance of the desired path.
[0055] At 620 milliseconds after the start of the event, the actual path is still within the calibrated tolerance of the desired path.
[0056] At 640 milliseconds after the start of the event, the actual path is still within the calibrated tolerance of the desired path.
[0057] At 660 milliseconds after the onset of the event, the combined lateral and longitudinal accelerations exceeded the surface's friction limits. Consequently, the actual path no longer matches the desired path, and the algorithm reduces the commanded acceleration to 0.85 g.
[0058] At 680 milliseconds after the start of the event, the actual path still does not match the desired path, so the commanded deceleration is reduced to 0.75 g.
[0059] At 700 milliseconds after the start of the event, the actual path still does not match the desired path, so the commanded deceleration is reduced to 0.70 g.
[0060] At 720 milliseconds after the start of the event, the actual displacement matches the calibrated tolerance to the desired displacement, so 0.6 g is commanded.
[0061] At 740 milliseconds after the start of the event, the actual path still does not match the desired path, so the commanded deceleration is reduced to 0.55 g.
[0062] At 760 milliseconds after the start of the event, the actual path still does not match the desired path, so the commanded deceleration is reduced to 0.50 g.
[0063] At 780 milliseconds after the start of the event, the actual path still does not match the desired path, so the commanded deceleration is reduced to 0.45 g.
[0064] At 800 milliseconds after the start of the event, the actual displacement is within the calibrated tolerance of the desired displacement, so 0.45 g is commanded.
[0065] At 820 milliseconds after the start of the event, the actual path does not match the desired path, so the commanded deceleration is reduced to 0.40 g.
[0066] At 840 milliseconds after the start of the event, the actual path does not match the desired path, so the commanded deceleration is reduced to 0.35 g.
[0067] At 860 milliseconds after the start of the event, the actual path does not match the desired path, so the commanded deceleration is reduced to 0.30 g.
[0068] At 880 milliseconds after the start of the event, the actual displacement is within the calibrated tolerance of the desired displacement, so 0.30 g is commanded.
[0069] During the next 300 milliseconds after the start of the event, the actual path is within the calibrated tolerance to the desired path and the resulting acceleration is near the friction limit that the tire-road interface can support, so 0.30 g is commanded.
[0070] At 1200 milliseconds, the actual travel is within the calibrated tolerance to the desired travel and the resulting acceleration has dropped far enough from the friction limit that the tire-road interface can support, so the level of commanded deceleration is increased to 0.35 g.
[0071] At 1220 milliseconds after the start of the event, the actual displacement is within the calibrated tolerance of the desired displacement, so 0.35 g is commanded.
[0072] The collision with the host vehicle occurs 1240 milliseconds after the start of the event. EXAMPLE 4 Motor vehicle driving on a highway entrance; driver brakes late
[0073] Motor vehicle 200 is moving along a circular highway entrance at a constant speed of 20 m / s. The radius of the entrance is 80 m, which results in a constant lateral acceleration of 5 m / s.2 In the merging lane of the entrance, there is a driver who, instead of merging onto the highway, has stopped his vehicle. The driver of the moving motor vehicle 200 is inattentive. If the collision is unavoidable, the CPS 210 issues a command to autonomously brake with maximum deceleration. The vehicle path control algorithm 100 becomes active. Initially, the desired yaw rate is slightly above 7 degrees / second. The actual yaw rate is also slightly above 7 degrees / second. The actual path is checked every 20 milliseconds and compared to the desired path until the event is over.
[0074] At 220 milliseconds after the onset of the event, the actual path does not match the desired path (understeer) and the vehicle path control algorithm reduces the commanded acceleration to 0.8 g.
[0075] At 240 milliseconds after the start of the event, the actual path still does not match the desired path, so the commanded deceleration is reduced to 0.7 g.
[0076] At 260 milliseconds after the start of the event, the actual path still does not match the desired path, so the commanded deceleration is reduced to 0.65 g.
[0077] At 280 milliseconds after the start of the event, the actual path still does not match the desired path, so the commanded deceleration is reduced to 0.60 g.
[0078] At 300 milliseconds after the start of the event, the actual path still does not match the desired path, so the commanded deceleration is reduced to 0.55 g.
[0079] At 320 milliseconds after the start of the event, the actual displacement is within the calibrated tolerance of the desired displacement, so 0.55 g is commanded.
[0080] At 340 milliseconds after the onset of the event, the driver applies the brakes to command a deceleration of 0.8 g. The driver now requests a higher deceleration than the CPS, so the actual trajectory is not compared to the desired trajectory.
[0081] At 360 milliseconds after the event starts, the driver requests a higher deceleration than the CPS, so the actual path is not compared to the desired path.
[0082] After every 20 milliseconds until the duration of the event, the driver requests a higher deceleration than the CPS, so that the actual vehicle path is not compared with the desired vehicle path and the commanded deceleration is not modified.
[0083] According to the foregoing description, the vehicle path control algorithm 100 according to the present invention is intended to ensure that the motor vehicle moves in the direction of the path of travel intended by the driver by adjusting the braking effect exerted by the CPS, the vehicle path control algorithm 100 operating independently of a stability control system, if present (of course, a data line is used from the command interpreter of Fig. 3B is merely considered as an exemplary illustration of a modality for providing necessary data to the CPS brake adjustment controller).
[0084] A stability control system (as discussed, for example, in U.S. Patent No. 5,941,919) is intended to provide vehicle stability by individually adjusting braking at the wheels and / or by adjusting engine power. As such, the brake controller follows commands from the stability control system if a conflict occurs with the braking adjustment by the vehicle path control algorithm 100.
[0085] Furthermore, the vehicle path control algorithm 100, of course, applies to autonomous braking in the sense that autonomous braking is in addition to driver-requested braking. For example, when autonomous braking is implemented by a CPS, the present invention discontinues braking in the event that the actual vehicle trajectory deviates at least substantially from the driver-intended vehicle trajectory, with the autonomous braking generally exceeding what the driver requests, if any.
Claims
[1] Movement path control method implemented during the activation of autonomous braking, comprising: Detecting an activation of autonomous braking of a motor vehicle (200) implemented by a collision preparation system (210) of the motor vehicle (200); Detecting a braking request from the driver; Detecting a movement path of the motor vehicle (200) intended by the driver during activation; detecting an actual movement path of the motor vehicle (200) during activation; Comparing the driver’s intended movement path with the actual movement path during activation; and adjusting the braking of the motor vehicle (200) if the actual path of travel differs from the path of travel intended by the driver, wherein the adjusting of the braking is intended to reduce the difference; characterized by : Detecting a CPS braking request from the collision preparation system (210); wherein the adjusting step is performed if further the driver braking request is less than the CPS braking request. [2] The method of claim 1, wherein the comparison is repeatedly performed during activation at a predetermined timing. [3] The method of claim 2, wherein the step of adjusting comprises reducing braking until the difference is reduced to zero. [4] The method of claim 1, further comprising: Detecting a CPS braking request from the collision preparation system (210); and Increase braking until braking equals the CPS braking request, provided this does not increase the difference. [5] The method of claim 4, further comprising: Detecting a driver braking request; wherein the adjusting step is performed if further the driver braking request is less than the CPS braking request. [6] The method of claim 5, wherein the timing is 20 milliseconds.
Citation Information
Patent Citations
Method for controlling a reversible occupant protection device in a motor vehicle
DE10121386C1
Method for improving the drivability of a vehicle
DE10244557A1
vehicle brake control device
DE10356501A1
Pre-collision assessment of potential collision severity for road vehicles
US20040254729A1
Chassis control system
US5941919A
