System and method for controlling a motor vehicle to negotiate a low obstacle
By designing low obstacle detection and control devices in automatic or semi-automatic parking systems, the problems of low obstacle detection difficulties and vehicle jumps in the prior art are solved, and a safe and robust low obstacle crossing and recovery of control systems are achieved. , improves the accuracy and safety of automatic parking.
Patent Information
- Application Number
- CN201980009566.1
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2018-01-31
- Filing Date
- 2019-01-24
- Publication Date
- 2024-11-01
- Estimated Expiration
- 2039-01-24
AI Technical Summary
Existing automatic or semi-automatic parking systems have difficulties in detecting low obstacles (such as sidewalks), which can cause vehicle jumps or collisions, and the closed-loop speed controller cannot effectively avoid safety constraint violations in saturation.
A control system is designed, including a low obstacle detection device and a control device for crossing low obstacles, and determines whether it is safe to cross the low obstacles by detecting the vehicle's speed, remaining distance, status and torque requests, and in success After passing, reinitialize the controller and cancel the engine torque request to restore the original track.
It realizes safe detection and crossing low obstacles during maneuvering, avoiding jumps and collisions, ensuring that the vehicle handles low obstacles steadily in parking assist control, improving the accuracy and safety of automatic parking.
Smart Images

Figure CN111655559B_ABST
Abstract
Description
Technical Field
[0001] The technical field of the invention is controlling a motor vehicle to park said vehicle. Background Art
[0002] Automatic or semi-automatic parking systems are based on surrounding detection systems (detection of free space and obstacles) operating with the aid of ultrasonic sensors and / or cameras.
[0003] The first technical difficulty is that this perception system is currently subject to many limitations in detecting low obstacles (such as sidewalks). During the spatial search phase, there is a certain threshold for the height of obstacles that the perception system can detect. If the low obstacle is above this threshold, the maneuver is performed with a trajectory that does not cross the obstacle. For example, in the case of a parallel parking maneuver, the vehicle is parked with the inner wheels parallel to the obstacle. If such a trajectory is not possible, the system will not provide the space. Therefore, the current implementation of the system can cause problems, especially when the parking space straddles the sidewalk and the road.
[0004] The second technical difficulty is associated with the fact that a closed-loop speed controller is provided and is responsible for moving the vehicle from a given position towards a parking space selected by the driver or by the parking system. Therefore, if this low obstacle of the sidewalk type is not detected, the system is hampered and the controller sends a torque request to the engine in response to the speed setpoint within the limits of the accepted values due to saturation. This saturation of the control loop is necessary to prevent the violation of the constraints associated with the safety of the maneuvers and effectively stops the vehicle against this low obstacle of the sidewalk type.
[0005] One solution would be to raise the saturation limit. The risk with this solution is that the vehicle will jump when passing over low obstacles, which could lead to collisions with objects around the vehicle.
[0006] This risk is unacceptable. Therefore, a robust strategy is needed to: detect during a maneuver that the car has stopped on a low obstacle of the sidewalk type that is present on the trajectory calculated by the perception system; to navigate the obstacle in a safe manner; and then to resume execution of the original trajectory calculated by the perception system.
[0007] In the prior art, document KR 20130089502 is known which describes a parking assistance system which provides for detection of a sidewalk on a parking space and recognition of the shape of the sidewalk in order to improve the accuracy of automatic parking.
[0008] Also known is document US 2016207528, which describes a method for autonomous maneuvering of a vehicle by voice command of a user. When at least one wheel of the vehicle encounters a vertical obstacle (of the sidewalk type) that has not been detected by the sensors providing information to the system, the assistance system enters an operating mode in which the speed setpoint is increased during the maneuver so that it is better suited to handling the obstacle.
[0009] The cited documents cannot solve the technical problem as described above. Summary of the invention
[0010] The object of the present invention is a system for controlling a motor vehicle to negotiate a low obstacle, the system interacting with a main controller including a speed controller for assisting in parking the motor vehicle. The control system comprises:
[0011] a low obstacle detection device configured to determine the presence of a low obstacle during operation of the parking assist controller and suspend operation of the main controller,
[0012] a control device for passing over a low obstacle, the control device being configured to determine an engine torque request for passing over a low obstacle upon receiving a low obstacle detection signal from the low obstacle detection device, the engine torque request for passing over the low obstacle being transmitted to a speed controller of the main controller, and the control device being configured to determine that the low obstacle is successfully passed over,
[0013] A main controller initialization device is configured to command the following operations when receiving a message indicating that the low obstacle has been successfully crossed: reinitializing the main controller, canceling the engine torque request for crossing the low obstacle, and resuming the operation of the main controller.
[0014] The low obstacle detection device may include: a speed detection device configured to transmit a first value from its output terminal when the estimated speed of the vehicle becomes lower than a threshold speed; a remaining distance detection device configured to transmit a first value from its output terminal when the remaining distance to be traveled received from the main controller is greater than a distance threshold; a state condition detection device configured to transmit a first value from its output terminal when the current operation step of the main controller is a step of controlling the speed of the vehicle; an odometer condition detection device configured to transmit a first value from its output terminal when the odometer data indicates that the vehicle is stationary; a torque request condition detection device configured to transmit a first value from its output terminal when the wheel torque request received from the main controller is greater than the wheel torque request threshold to ensure that the driver or the system wants to make the vehicle at the desired speed. a first value transmitted from its output terminal when the vehicle moves forward in the direction of the engaged gear; an AND logic gate configured to transmit the first value from its output terminal when the first value is received from the odometer condition detection device and the torque request condition detection device at the same time; a timing device configured to determine whether the first value has been received from the AND logic gate during a predetermined time interval, and if so, transmit the first value from its output terminal; a second AND logic gate configured to transmit the first value from its output terminal when the first value is received from the speed detection device, the remaining distance detection device, the state condition detection device and the timing device at the same time; and a second timing device configured to determine whether the first value has been received from the second AND logic gate during a predetermined time interval, and if so, transmit the low obstacle detection signal from its output terminal.
[0015] The control device for negotiating a low obstacle may include: a main controller receiving a low obstacle detection signal at its input, means for controlling the stopping of the vehicle, means for distance estimation, an engine torque calculation means configured to determine an engine torque request for negotiating the low obstacle,
[0016] The main controller is capable of controlling the vehicle stop control device, the distance estimation device and the engine torque calculation device to transmit a braking command, determine a distance traveled, determine whether the low obstacle has been crossed based on the distance traveled, determine a wheel torque request if the obstacle has not been crossed, and determine a main controller reinitialization message if the obstacle has been crossed.
[0017] Another object of the invention is a method for controlling a motor vehicle to pass a low obstacle, which method interacts with a method for controlling a motor vehicle to assist in parking by speed control. The method comprises the following steps:
[0018] detecting the presence of a low obstacle upon which the vehicle is stopped, and suspending operation of the parking assist control method,
[0019] commanding a traverse of the low obstacle by determining a torque request for traversing the low obstacle,
[0020] Commands are provided to reinitialize the parking assist control method, cancel the engine torque request for negotiating the low obstacle, and resume operation of the parking assist control method.
[0021] To detect the presence of a low obstacle on which the vehicle is stopped, the following steps may be performed:
[0022] If all conditions in the first set of conditions are verified, then determining that the first variable is equal to the first value,
[0023] If all conditions in the second set of conditions are verified during the predetermined time interval, determining that the second variable is equal to the first value,
[0024] If the first variable and the second variable take the first value during a predetermined time interval, it is determined that the vehicle has passed the low obstacle,
[0025] This first set of conditions includes:
[0026] - determining whether the estimated speed of the vehicle is below a threshold speed,
[0027] - determining whether the remaining distance to be traveled by the vehicle received from the parking assistance control method is higher than a threshold value of the remaining distance to be traveled,
[0028] - determining whether the current state of the parking assistance control method is equal to the step of controlling the speed of the vehicle,
[0029] This second set of conditions includes:
[0030] - determining whether the vehicle is stationary by comparing the odometer data to a threshold,
[0031] - determining whether a wheel torque request received from the parking assist control method is above a wheel torque request threshold.
[0032] To control the clearance over low obstacles, the following steps may be performed:
[0033] Transmits brake command,
[0034] Determine the distance traveled,
[0035] determining whether the low obstacle has been crossed based on the distance traveled,
[0036] If this is not the case, a torque request is determined for overcoming the low obstacle.
[0037] If this is the case, the parking assistance control method is reinitialized.
[0038] The engine torque request for negotiating the low obstacle may be determined based on a mathematical model of the forces exerted by the low obstacle on the wheels of the vehicle when negotiating the low obstacle and based on the dynamics of the actuators.
[0039] The engine torque request for negotiating the low obstacle may include a first component determined when the obstacle is detected and a second component determined after a predetermined time interval is estimated from when the obstacle is detected.
[0040] To allow for gradients, the wheel torque request over the low obstacle may be compensated by considering only the horizontal component of the torque request.
[0041] If the determined torque request for traversing the low obstacle still cannot achieve traversal of the low obstacle, stopping of the vehicle by braking may be commanded and a message transmitted to the parking assist control method indicating that the obstacle cannot be traversed, resulting in cancellation of the current maneuver.
[0042] If the low obstacle is successfully traversed, a message may be transmitted to reinitialize the master controller and the engine torque request to traverse the low obstacle may be cancelled.
[0043] A successful traversal of the low obstacle may be detected when the estimate of the distance traveled by the vehicle is above a predetermined threshold.
[0044] The predetermined threshold may be equal to a distance that is greater than a detection capability of the perception system for estimating the distance between the vehicle and the low obstacle.
[0045] By comparing the measured value of the longitudinal acceleration of the vehicle with a calibrated threshold value, a successful traversal of the low obstacle can be detected.
[0046] The threshold value may be calculated based on the direction of movement of the vehicle.
[0047] In addition to multiplying the scenarios that qualify for parking assistance, the solution also has the advantage of being compatible with existing architectures. Thus, since processing sensors or proprioceptive sensors are already present in the vehicle according to the existing architecture, almost no additional resources are required in terms of these sensors.
[0048] The detection is also robust to road types, especially roads with gradients. BRIEF DESCRIPTION OF THE DRAWINGS
[0049] Other objects, characteristics and advantages of the present invention will become apparent from a reading of the following description given by way of non-limiting example only and with reference to the accompanying drawings, in which:
[0050] - Figure 1 The main operation steps of the main controller according to the prior art are shown.
[0051] - Figure 2 shows the main elements of a control system for negotiating low obstacles,
[0052] - Figure 3 shows the main elements of the pedestrian detection device,
[0053] - Figure 4 The main elements of the device for controlling the crossing of a walkway are shown. DETAILED DESCRIPTION
[0054] The invention relates to a strategy for detecting the stopping of a vehicle against a low obstacle during a semi-automatic or automatic parking maneuver. By "low obstacle" is meant in particular a pedestrian path or any obstacle that the vehicle can pass over. After this detection, a method for passing over said low obstacle is started. The module is integrated into a control law based on a polystate adaptive controller. The controller comprises a stage for switching from open-loop control to closed-loop control.
[0055] The main technical difficulty is to detect the actual stop against a low obstacle during the maneuver to avoid false detections. Therefore, the detection strategy must be robust for such scenarios. The detection strategy must be able to distinguish the vehicle stop determined by the driver from an involuntary stop, and when the maneuver occurs on a road with a gradient, it must also be able to distinguish the stop against a low obstacle from the vehicle's slip. Obviously, another difficulty is that the obstacle must be crossed quickly and safely. Any jump at the end of the crossing needs to be avoided, which may cause a collision. Finally, the detection and crossing of low obstacles during the parking maneuver must be incorporated into a more general control law for controlling the longitudinal speed of the vehicle during the maneuver. Therefore, it is necessary to provide good synchronization and good switching between the controller and the modules described in the present invention.
[0056] Such a control law for speed control is described in French patent application FR1751873 filed on behalf of RENAULT sas on March 8, 2017. The application describes a multi-state controller for assisting a parked motor vehicle, in which a motor vehicle control system for negotiating low obstacles is incorporated. The controller comprises five main states, denoted E1 to E5 ( Figure 1 shown).
[0057] The control system 1 for negotiating low obstacles is active only during the control of the vehicle speed corresponding to step E3, which begins at the end of complete cancellation of the acceleration setpoint or when the parking assistance system detects movement of the vehicle. In the remainder of the description, the term "primary controller" is used to refer to the multi-state controller according to the present patent application.
[0058] The operation of the control system 1 for negotiating low obstacles requires suspending the operation of the main controller 2 , as described in French patent application FR 1 751 873 .
[0059] exist Figure 2 The control system 1 for crossing low obstacles shown in the figure comprises a device 6 for detecting low obstacles, which is connected to a device 7 for controlling crossing low obstacles, which itself is connected to a device 8 for initializing a main controller. The device 8 provides the function of pausing the main controller and the function of initializing the same controller to resume the execution of the current maneuver. The main controller initialization device 8 receives a low obstacle detection signal at its input, represented by SidewalkDetected. When the car stops on a low obstacle of the sidewalk type, the initialization device 8 detects that the signal switches to a first value and initiates the suspension of the main controller. Subsequently, when a ResetPIDFFD / TakeOff signal taking a first value is received after detecting that the low obstacle has been successfully crossed, the initialization device 8 reinitializes the main controller.
[0060] The control system 1 for negotiating low obstacles receives at its input the vehicle's odometer Veh_odo, the vehicle's estimated speed Veh_speed, and information related to the main controller, such as the state of the main controller RegulatorState, the wheel torque request PWTRequestedTrq calculated by the main controller, and the stopping distance StoppingDistance.
[0061] The low obstacle detection device 6 generates a low obstacle detection signal (denoted as SidewalkDetected) which takes a first value when the car stops on a low obstacle of the sidewalk type. This signal is then used by the control device 7 for crossing a low obstacle having the function of initializing a speed controller included in the main controller 2, so as to provide synchronization, calculate the engine torque to be transmitted for crossing the low obstacle, and finally determine the successful crossing of the low obstacle and reinitialize the main speed controller to resume the execution of the current maneuver. Synchronization is provided by the following operations: verifying the operation steps executed by the main controller, pausing the main controller to activate the control system 1 for avoiding low obstacles, and resuming execution when the control system 1 for crossing the low obstacle has completed its processing.
[0062] Figure 3 The low obstacle detection device 6 shown in receives the vehicle's speed Veh_speed, the odometer Veh_odo, the wheel torque request PWTRequestedTrq and the state RegulatorState of the main controller. The use of "odometer" refers to a "wheel top" type of mobile sensor of the vehicle, which transmits a pulse every time a fixed mark on the wheel passes a fixed detector. Since the circumference of the wheel is known, the distance traveled by the wheel rotation between two pulses is known. The odometer also includes a direction sensor, which can be used to determine whether it is moving toward the front of the vehicle or toward the rear of the vehicle. When the movement of the wheel during a predetermined time interval is essentially zero, that is, below a threshold, it is determined that the vehicle remains stationary.
[0063] Finally, the state of the main controller 2, RegulatorState, corresponds to the current state of the main controller 2 (eg Figure 1 (as shown in steps E0 to E4 of FIG. 1 ).
[0064] The low obstacle detection device 6 includes a plurality of detection devices 6a, 6b, 6c, 6d, and 6e.
[0065] The speed detection device 6a compares the estimated speed Veh_speed of the vehicle with the threshold speed V th Compare to determine whether the following conditions are met.
[0066] Veh_speed<V th (Equation 1)
[0067] Therefore, when the estimated speed Veh_speed becomes smaller than the threshold speed V th (selected to be lower), the speed detection device 6a delivers a first value from its output terminal.
[0068] The estimated speed is calculated based on the odometer data present on the vehicle's CAN bus, which includes wheel crests corresponding to the passage of a position indicator on at least one wheel. The principle is based on the time T elapsed between the appearance of two wheel crests. 2顶 For each vehicle, the distance Dist between two consecutive wheel tops is precisely known. 2顶 . The estimated speed is derived from it by the following calculation:
[0069] Veh_speed=(Dist 2顶 ) / T 2顶 (Equation 2)
[0070] The remaining distance detection device 6b receives at its input the remaining distance StoppingDistance that the vehicle will travel from the perception and trajectory calculation system, and compares the remaining distance with the threshold value RemainingDist Th (remaining distance threshold) to check whether the following conditions are met:
[0071] StoppingDistance>RemainingDist Th (Equation 3)
[0072] Therefore, when the remaining distance to be traveled StoppingDistance becomes greater than the distance threshold RemainingDist Th , the remaining distance detection device 6 b transmits a first value from its output. Thus, if the end of the space is reached and only a distance less than or equal to the distance threshold RemainingDist_Th remains to be travelled, any detection of a low obstacle of the sidewalk type is distinguished.
[0073] If the system does not detect a low obstacle and there is a distance less than or equal to the distance threshold RemainingDist_Th(m) left to travel, the remaining distance detection device 6b informs the main controller 2 that it is not possible to continue moving in this direction. In turn, the main controller then informs the perception and trajectory calculation system of this impossible situation, in which case the perception and trajectory calculation system will evaluate continuing the maneuver in the opposite direction.
[0074] The state condition detection device 6c receives at its input the current step of the controller, denoted as RegulatorState. The state condition detection device 6c then determines whether the main controller 2 is in Figure 1 If this is the case, the state condition detection device 6c delivers a first value from its output.
[0075] By means of this condition it is ensured that the detection and overcoming of an obstacle will not be activated outside of a state where the controller is controlling the speed of the vehicle.
[0076] The odometer condition detection device 6d compares the odometer data available on the CAN bus with predefined values. The odometer data includes wheel tops for determining the travel distance and the direction of movement to determine the direction in which each movement is performed (forward or backward). Based on the result of the comparison, it is determined whether the vehicle is stationary and therefore whether the vehicle may be stopped against an obstacle. If this is the case, the odometer condition detection device 6d transmits a first value from its output.
[0077] The torque request condition detection device 6e receives at its input the wheel torque request PWTRequestedTrq from the main controller 2 and determines whether the wheel torque request PWTRequestedTrq is above a wheel torque request threshold value to determine whether the driver or the system wishes to move the vehicle forward in the direction of the engaged gear. If this is the case, the torque request condition detection device 6e delivers a first value from its output.
[0078] In one embodiment, the compensated wheel torque request is determined to be equal to the horizontal component of the torque request. Then, selecting the torque threshold becomes easy.
[0079] The AND logic gate (indicated as 6f) receives the values transmitted by the odometer condition detection device 6d and the torque request condition detection device 6e at its input terminals. When the first value is received from the odometer condition detection device 6d and the torque request condition detection device 6e at the same time, the AND logic gate (indicated as 6f) transmits the first value from its output terminal. In other cases, the AND logic gate (indicated as 6f) transmits the second value from its output terminal.
[0080] The timing device 6g connected to the output of the AND logic gate 6f determines whether the signal received from the AND logic gate during the predetermined time interval corresponds to the simultaneous verification of the odometer condition and the torque request condition. In other words, the timing device 6g determines whether the first value is received from the AND logic gate 6f during the predetermined time interval.
[0081] If this is the case, the timing device 6g delivers a first value from its output. Otherwise, the timing device 6g delivers a second value.
[0082] The second AND logic gate (designated 6h) receives at its input the values delivered by the speed detection means 6a, the remaining distance detection means 6b, the state condition detection means 6c and the timing means 6g.
[0083] When receiving the first value from the speed detection device 6a, the remaining distance detection device 6b, the state condition detection device 6c and the timing device 6g at the same time, the second AND logic gate (denoted as 6h) transmits the first value from its output terminal. In other cases, the second AND logic gate (denoted as 6h) transmits the second value from its output terminal.
[0084] The second timing device 6i connected to the output of the second AND logic gate 6h determines whether the signal received from the second AND logic gate 6h during a predetermined time interval corresponds to the first value.
[0085] If this is the case, the second timing means 6i delivers the first value from its output. Otherwise, the second timing means 6i delivers the second value.
[0086] The signal at the output of the second timing device 6i corresponds to the low obstacle detection signal SidewalkDetected.
[0087] Now refer to Figure 4 A control device 7 for negotiating a low obstacle is described, which is connected to an output of the low obstacle detection device 6 and receives a low obstacle detection signal SidewalkDetected.
[0088] After the presence of an obstacle is confirmed by the low obstacle detection device 6 via the low obstacle detection signal SidewalkDetected, the control device 7 for passing over a low obstacle arranges all actions.
[0089] To this end, the control device 7 for negotiating a low obstacle comprises a main controller 7 a which receives at its input a low obstacle detection signal SidewalkDetected originating from the low obstacle detection device 6 .
[0090] If the low obstacle detection signal SidewalkDetected takes the first value, the main controller 7a controls the vehicle stop control device 7b to transmit a braking command. The vehicle stop control device 7b also verifies the braking state of the vehicle via information from the CAN, in particular information on whether the vehicle remains stationary.
[0091] The main controller 7a then controls the distance estimation means 7c to determine successful crossing of the low obstacle based on the distance travelled and the initialisation value Crosseddistance_initialisation transmitted by the main controller 7a.
[0092] In response, if this is the case, the distance estimation means 7c transmits to the main controller 7a a message sidewalk_crossed indicating that the low obstacle has been crossed.
[0093] In parallel with the initialization estimation device 7c, the main controller 7a controls the engine torque calculation device 7d to initialize the speed controller of the main controller 2. The engine torque request SidewalkTrqReq for crossing the low obstacle is determined in the context of synchronization and then transmitted to the speed controller of the main controller. In other words, the engine torque request SidewalkTrqReq for crossing the low obstacle is transmitted to the speed controller of the main controller while suspending the operation of the main controller. To this end, the engine torque calculation device 7d uses a mathematical model of the force applied by the low obstacle to the wheels of the vehicle when crossing to determine the engine torque request SidewalkTrqReq for crossing the low obstacle. Among other factors, a low obstacle of the sidewalk type generates a resistance to the wheel that is proportional to its size and the vehicle dynamics. Therefore, it is necessary to generate an engine torque set point for overcoming this resistance torque, which must be higher when the vehicle is loaded. By using adjustment parameters, the dynamics of the actuator can also be taken into account. Then, the expression of the engine torque request SidewalkTrqReq for crossing the low obstacle is as follows:
[0094]
[0095] in:
[0096] α: Speed factor for the torque set point, defines the speed at which the desired torque level is reached. It is a time constant.
[0097] k: sampling time.
[0098] Te: sampling period.
[0099] K_swk: Setpoint gain, defines the torque level to be achieved.
[0100] In another embodiment, the engine torque request SidewalkTrqReq for traversing a low obstacle is calculated in a different manner when the obstacle is detected and when the obstacle has not been traversed after a certain time delay.
[0101] The engine torque request SidewalkTrqReq_bf for traversing a low obstacle during detection is defined by the following equation:
[0102]
[0103] The engine torque request SidewalkTrqReq_af for passing over a low obstacle after a certain time delay is defined by the following equation:
[0104]
[0105] in:
[0106] K1 swk : Gain of the torque setpoint on the first part, defines the torque level to be achieved.
[0107] K2 swk : Gain of the torque setpoint on the second part, defining the torque level to be achieved.
[0108] If the torque request calculated in this way still cannot achieve the crossing of the low obstacle, the engine torque calculation device 7d sends a failure message SidewalkFailure to the main controller 7a. Upon receiving this message, the main controller 7a sends a braking command StopVehicle to the vehicle stop control device 7b, and transmits a message Cancel_imp indicating that the obstacle cannot be crossed to the main controller 2, resulting in cancellation of the current maneuver.
[0109] If the low obstacle has been successfully crossed, the main controller 7a receives a message indicating that the low obstacle has been crossed from the distance estimation means 7c, denoted as Sidewalk_Crossed. The main controller 7a then transmits a message for reinitializing the main controller to the means 8 for initializing the main controller, denoted as ResetPIDFFD / TakeOff.
[0110] In one embodiment, the detection of a successful crossing by the distance estimation means 7c is performed by comparing the estimate of the distance travelled by the vehicle with a threshold slightly above the detection capabilities of the perception system. This enables limiting the current manoeuvre if the obstacle is particularly low and does not cause a significant change in torque.
[0111] In another embodiment, the detection of crossing a low obstacle can be performed by comparing the longitudinal acceleration of the vehicle obtained from sensors installed on all production vehicles with a calibrated threshold. The threshold is calculated based on the direction of movement of the vehicle. As long as the measured acceleration is above the threshold, the crossing estimation device 7c transmits a message "SidewalkCrossed" carrying a first value indicating that a low obstacle has been crossed. This method of detecting a successful crossing is more robust because during the crossing of an obstacle, the vehicle may make short forward and backward movements that are difficult for the estimation device 7c to interpret based on distance logic. In this case, the estimation device 7c based on distance logic usually considers that there is progress in one direction and then considers that there is progress in the other direction, which prevents the distance condition from being achieved.
[0112] The master controller initialization device 8 then receives the re-initialization message ResetPIDFFD / TakeOff and transmits it to the master controller 2. Figure 2 The message represented as SwkTrqReset (Swk torque request) in the command is to perform the following operations: reinitialize the main controller 2, cancel the engine torque request SidewalkTrqReq for crossing the low obstacle, and resume the operation of the main controller 2 (such as Figure 1 As shown). The main controller initialization device 8 interprets the processing of the re-initialization message ResetPIDFFD / Take as follows: the entire step of pausing and re-initializing the main controller 2 only needs to be executed at the moment when SidewalkDetected and ResetPIDFFD / TakeOff switch to the first value, and is not executed continuously.
Claims
1. A system for controlling a motor vehicle to negotiate a low obstacle, the system interacting with a main controller (2) including a speed controller for assisting in parking the motor vehicle, characterized in that The system includes: a low obstacle detection device (6) configured to determine the presence of a low obstacle during operation of the main controller and to suspend operation of the main controller (2), a control device (7) for passing over a low obstacle, the control device being configured to determine an engine torque request for passing over a low obstacle when receiving a low obstacle detection signal from the low obstacle detection device (6), the engine torque request for passing over the low obstacle being transmitted to a speed controller of the main controller (2), and the control device being configured to determine whether the low obstacle has been passed over successfully, means (8) for initializing the main controller (2), the means being configured to, upon receiving a message indicating successful traversal of the low obstacle, command the following operations: reinitializing the main controller (2), cancelling the engine torque request for traversing the low obstacle, and resuming operation of the main controller (2), Wherein, the low obstacle detection device (6) comprises: speed detection means (6a) configured to transmit a first value from its output when the estimated speed of the vehicle becomes lower than a threshold speed, means (6b) for detecting a remaining distance, the means being configured to transmit a first value from its output terminal when the remaining distance to be travelled received from the main controller (2) is greater than a distance threshold, means (6c) for detecting a state condition, the means being configured to transmit a first value from its output terminal when the current operation step of the main controller (2) is a step of controlling the speed of the vehicle, means (6d) for detecting an odometer condition, the means being configured to transmit a first value from its output when the odometer data indicates that the vehicle is stationary, means (6e) for detecting a torque request condition, the means being configured to transmit a first value from its output when a vehicle torque request received from the main controller (2) is above a wheel torque request threshold to determine whether the driver or the system wishes to move the vehicle forward in the direction of the engaged gear, an AND logic gate (6f) configured to transmit a first value from its output terminal when the first value is received from both the odometer condition detection device (6d) and the torque request condition detection device (6e), timing means (6g) configured to determine whether the first value is received from the AND logic gate (6f) during a predetermined time interval and, if this is the case, to transmit the first value from its output, a second AND logic gate (6h) configured to transmit a first value from its output terminal when the first value is received simultaneously from the speed detection device (6a), the remaining distance detection device (6b), the state condition detection device (6c) and the timing device (6g), and Second timing means (6i) are configured to determine whether the first value is received from the second AND logic gate (6h) during a predetermined time interval and, if this is the case, to transmit the low obstacle detection signal from its output.
2. The system of claim 1, wherein: The control device (7) for crossing a low obstacle comprises: a main controller (7a) receiving the low obstacle detection signal at its input, a vehicle stop control device (7b) for controlling the stop of the vehicle, distance estimating means (7c) for estimating the distance, an engine torque calculation device (7d) configured to determine the engine torque request for traversing the low obstacle, The main controller (7a) is capable of controlling the vehicle stop control device (7b), the distance estimation device (7c) and the engine torque calculation device (7d) to transmit a braking command, determine the distance traveled, determine whether the low obstacle has been crossed based on the distance traveled, determine the wheel torque request if the obstacle has not been crossed, and determine a main controller (2) reinitialization message if the obstacle has been crossed.
3. A control method for controlling a motor vehicle to pass a low obstacle, the control method interacting with a parking assistance control method for assisting parking the motor vehicle by speed control, the control method comprising the following steps: detecting the presence of a low obstacle upon which the vehicle is stopped, and suspending operation of the parking assist control method, commanding a traverse of the low obstacle by determining a torque request for traversing the low obstacle, commanding the following operations: reinitializing the parking assist control method, canceling the engine torque request for negotiating the low obstacle, and resuming operation of the parking assist control method, In order to detect the presence of a low obstacle on which the vehicle is stopped, the following steps are performed: If all conditions in the first set of conditions are verified, then determining that the first variable is equal to the first value, If all conditions in the second set of conditions are verified during the predetermined time interval, determining that the second variable is equal to the first value, If the first variable and the second variable take the first value during a predetermined time interval, it is determined that the vehicle has passed the low obstacle, This first set of conditions includes: - determining whether the estimated speed of the vehicle is below a threshold speed, - determining whether the remaining distance to be traveled by the vehicle received from the parking assistance control method is higher than a threshold value of the remaining distance to be traveled, - determining whether the current state of the parking assistance control method is equal to the step of controlling the speed of the vehicle, This second set of conditions includes: - determining whether the vehicle is stationary by comparing the odometer data to a threshold, - determining whether a wheel torque request received from the parking assist control method is above a wheel torque request threshold.
4. The control method according to claim 3, wherein: To control the passage over this low obstacle: Transmits brake command, Determine the distance traveled, determining whether the low obstacle has been crossed based on the distance traveled, If this is not the case, a torque request is determined for overcoming the low obstacle. If this is the case, the parking assistance control method is reinitialized.
5. The control method according to claim 4, wherein: The engine torque request for traversing the low obstacle is determined based on a mathematical model of the forces exerted by the low obstacle on the wheels of the vehicle when traversing the low obstacle and based on the dynamics of the actuators.
6. The control method according to claim 5, wherein: The engine torque request for negotiating the low obstacle includes a first component determined when the obstacle is detected and a second component determined after a predetermined time interval from when the obstacle is detected.
7. The control method according to claim 5, wherein: To allow for gradients, the wheel torque request over the low obstacle is compensated by considering only the horizontal component of the torque request.
8. The control method according to any one of claims 4 to 7, wherein: If the determined torque request for traversing the low obstacle still cannot achieve traversal of the low obstacle, The vehicle is then commanded to stop by braking, and a message is transmitted to the parking assistance control method indicating that the obstacle cannot be traversed, resulting in cancellation of the current maneuver.
9. The control method according to claim 4, wherein: If the low obstacle is successfully traversed, a message is transmitted to reinitialize the master controller for assisting in parking the motor vehicle, and the engine torque request for traversing the low obstacle is cancelled.
10. The control method according to any one of claims 4 to 7, wherein: A successful traversal of the low obstacle is detected when the estimate of the distance traveled by the vehicle is above a predetermined threshold.
11. The control method according to claim 10, wherein: The predetermined threshold is equal to a distance that is greater than a detection capability of a perception system used to estimate the distance between the vehicle and the low obstacle.
12. The control method according to any one of claims 4 to 7, wherein: Successful traversal of the low obstacle is detected by comparing the measurement of the longitudinal acceleration of the vehicle to a calibrated threshold.
13. The control method according to claim 12, wherein: The threshold is calculated based on the direction of movement of the vehicle.
