The present invention generally relates to systems for assisting an operator in backing a trailer, and more particularly, to systems using imager-based hitch angle detection.
Reversing a vehicle while towing a trailer can be challenging for many drivers, particularly for drivers that drive with a trailer on an infrequent basis or with various types of trailers. Some systems used to assist an operator in backing a trailer rely on hitch angle measurements to determine the position of the trailer relative to the vehicle. Thus, the accuracy and reliability of the hitch angle measurements can be critical to the operation of the trailer backup assist system. In systems employing imager-based hitch angle detection, improper calibration of an imaging device can lead to inaccurate hitch angle measurements. Furthermore, in instances where the imaging device becomes obstructed, such systems may be forced offline and rendered unable to determine a hitch angle between the vehicle and the trailer. To function properly, some systems require a user to input measurements such as trailer length. This is not only cumbersome on the user but may lead to erroneous measurements being inputted to the system. Accordingly, there is a need for a trailer backup assist system that overcomes the problems mentioned above. The present disclosure is intended to satisfy this need.
According to a first aspect of the present invention, a calibration method is provided herein. The method includes the steps of: using an imaging device to capture an image of a rear bumper; and providing a controller configured to process the captured image, identify a boundary separating the rear bumper from a ground; compare the identified boundary to an ideal boundary, and determine an offset between the identified boundary and the ideal boundary.
Embodiments of the first aspect can include any one or a combination of the following features:
According to a second aspect of the present invention, a trailer backup assist system is provided. The system includes a device configured to sense a trailer and a controller configured to determine a hitch angle between a vehicle and the trailer based on data provided by the device. If the device fails, the controller predicts the hitch angle based on a last known hitch angle, a last known angular velocity of the trailer, and an execution cycle time.
Embodiments of the second aspect can include one or a combination of the following features:
According to a third aspect of the present invention, a method of determining hitch angle between a vehicle and a trailer is provided. The method includes the steps of: selecting at least one hitch angle detection method amongst a plurality of hitch angle detection methods; using the selected at least one hitch angle detection method to determine a hitch angle between a vehicle and a trailer; and transitioning to another hitch angle detection method in the event the selected at least one hitch angle detection method becomes unavailable.
Embodiments of the third aspect can include one or a combination of the following features:
According to a fourth aspect of the present invention, a trailer backup assist system is provided. A steering input device is configured to provide a curvature command based on user input. A controller is configured to estimate a trailer length based on a vehicle and trailer yaw rate. The controller generates a steering command based on the estimated trailer length, the curvature command, a maximum steering angle, and a vehicle speed. The generated steering command is invariant to the estimated trailer length under certain conditions.
Embodiments of the fourth aspect can include one or a combination of the following features:
These and other features, advantages, and objects of the present invention will be further understood and appreciated by those skilled in the art by reference to the following specification, claims, and appended drawings.
In the drawings:
For purposes of description herein, it is to be understood that the disclosed trailer backup assist system and the related methods may assume various alternative embodiments and orientations, except where expressly specified to the contrary. It is also to be understood that the specific devices and processes illustrated in the attached drawings, and described in the following specification, are simply exemplary embodiments of the inventive concepts defined in the appended claims. While various aspects of the trailer backup assist system and the related methods are described with reference to a particular illustrative embodiment, the disclosed invention is not limited to such embodiments, and additional modifications, applications, and embodiments may be implemented without departing from the disclosed invention. Hence, specific dimensions and other physical characteristics relating to the embodiments disclosed herein are not to be considered as limiting, unless the claims expressly state otherwise.
As used herein, the term “and/or,” when used in a list of two or more items, means that any one of the listed items can be employed by itself, or any combination of two or more of the listed items can be employed. For example, if a composition is described as containing components A, B, and/or C, the composition can contain A alone; B alone; C alone; A and B in combination; A and C in combination; B and C in combination; or A, B, and C in combination.
Referring to
The TBA system 10 also includes an imaging device 34 located at the rear of the vehicle 12 and configured to image a rear-vehicle scene. The imaging device 34 may be centrally located at an upper region of a vehicle tailgate 35 such that the imaging device 34 is elevated relative to the tongue 26 of the trailer 14. The imaging device 34 has a field of view 36 located and oriented to capture one or more images that may include the tongue 26 of the trailer 14 and the hitch ball 30, among other things. Image data is supplied to a controller 38 of the TBA system 10 and is processed by the controller 38 to determine the hitch angle between the vehicle 12 and the trailer 14. Additional information regarding image-based hitch angle detection and associated methodologies can be found in commonly assigned U.S. Pat. No. 9,610,975 to Hu et al., issued Apr. 4, 2017, and entitled “HITCH ANGLE DETECTION FOR TRAILER BACKUP ASSIST SYSTEM,” the entire disclosure of which is incorporated by reference herein.
The controller 38 is configured with a microprocessor 40 and/or other analog and/or digital circuitry for processing one or more logic routines stored in a memory 42. The logic routines may include a hitch angle detection routine 44, an operating routine 46, and a curvature routine 47. Information from the imaging device 34 or other components of the TBA system 10 can be supplied to the controller 38 via a communication network of the vehicle 12, which can include a controller area network (CAN), a local interconnect network (LIN), or other conventional protocols used in the automotive industry. It should be appreciated that the controller 38 may be a stand-alone dedicated controller or may be a shared controller integrated with the imaging device 34 or other component of the TBA system 10 in addition to any other conceivable onboard or off-board vehicle control systems.
With respect to the present embodiment, the controller 38 is configured to communicate with a variety of vehicle equipment. The TBA system 10 may include a vehicle sensor module 48 that monitors certain dynamics of the vehicle 12. The vehicle sensor module 48 may generate a plurality of signals that are communicated to the controller 38 such as a vehicle speed signal generated by a speed sensor 50 and a vehicle yaw rate signal generated by a vehicle yaw rate sensor 52. A trailer sensor module 53 is provided that monitors certain dynamics of the trailer 14. The trailer sensor module 53 includes a trailer yaw rate sensor 54 configured to generate a trailer yaw rate signal that is provided to the controller 38.
A steering input device 55 is provided to enable a driver to control or otherwise modify a desired curvature (e.g., desired curvature 56;
The knob 58 may be rotatable about a rotational axis extending through a top surface or face of the knob 58. In other embodiments, the knob 58 may be rotatable about a rotational axis extending substantially parallel to a top surface or face of the knob 58. Furthermore, the steering input device 55, according to additional embodiments, may include alternative devices for providing the desired input, such as a joystick, a keypad, a series of depressible buttons or switches, a sliding input device, various user interfaces on a touch-screen display, a vision-based system for receiving gestures, a control interface on a portable device, and other conceivable input devices as generally understood by one having ordinary skill in the art. It is contemplated that the steering input device 55 may also function as an input device for other features, such as providing inputs for other vehicle features or systems.
According to one embodiment, the controller 38 of the TBA system 10 may control the power assist steering system 57 of the vehicle 12 to operate steered wheels 60 of the vehicle 12 for moving the vehicle 12 in such a manner that the trailer 14 reacts in accordance with the desired curvature 56 of the backing path of the trailer 14. The power assist steering system 57 may be an electric power-assisted steering (EPAS) system that includes an electric steering motor 62 for turning the steered wheels 60 to a steering angle based on a steering command generated by the controller 38, whereby the steering angle may be sensed by a steering angle sensor 64 of the power assist steering system 57 and provided to the controller 38. The steering command may be provided for autonomously steering the vehicle 12 during a backup maneuver and may alternatively be provided manually via a rotational position (e.g., a steering wheel angle) of a steering wheel 66 or the rotatable knob 58. However, in some embodiments, the steering wheel 66 of the vehicle 12 may be mechanically coupled with the steered wheels 60 of the vehicle 12, such that the steering wheel 66 moves in concert with steered wheels 60 via an internal torque, thereby preventing manual intervention with the steering wheel 66 during autonomous steering of the vehicle 12. In such instances, the power assist steering system 57 may include a torque sensor 68 that senses torque (e.g., gripping and/or turning) on the steering wheel 66 that is not expected from autonomous control of the steering wheel 66 and therefore indicative of manual intervention by the driver. In some embodiments, external torque applied to the steering wheel 66 may serve as a signal to the controller 38 that the driver has taken manual control and for the TBA system 10 to discontinue autonomous steering functionality.
The controller 38 of the TBA system 10 may also communicate with a vehicle brake control system 70 of the vehicle 12 to receive vehicle speed information such as individual wheel speeds of the vehicle 12. Additionally or alternatively, vehicle speed information may be provided to the controller 38 by a powertrain control system 72 and/or the speed sensor 50, among other conceivable means. It is conceivable that individual wheel speeds may be used to determine a vehicle yaw rate, which can be provided to the controller 38 in the alternative, or in addition to, the vehicle yaw rate measured by yaw rate sensor 52 of the vehicle sensor module 48. In some embodiments, the controller 38 may provide braking commands to the vehicle brake control system 70, thereby allowing the TBA system 10 to regulate the speed of the vehicle 12 during a backup maneuver of the trailer 14. It should be appreciated that the controller 38 may additionally or alternatively regulate the speed of the vehicle 12 via interaction with the powertrain control system 72.
Through interaction with the power assist steering system 57, the vehicle brake control system 70, and/or the powertrain control system 72 of the vehicle 12, the potential for unacceptable trailer backup conditions can be reduced. Examples of unacceptable trailer backup conditions include, but are not limited to, a vehicle over-speed condition, a high hitch angle rate, hitch angle dynamic instability, a trailer jackknife condition, sensor failure, and the like. In such circumstances, the driver may be unaware of the failure until the unacceptable trailer backup condition is imminent or already happening. Therefore, it is disclosed herein that the controller 38 of the TBA system 10 can generate an alert signal corresponding to a notification of an actual, impending, and/or anticipated unacceptable trailer backup condition, and prior to driver intervention, generate a counter measure to prevent such an unacceptable trailer backup condition.
According to one embodiment, the controller 38 may communicate with one or more devices, including a vehicle alert system 74, which may prompt visual, auditory, and tactile warnings. For instance, vehicle brake lights 76 and vehicle emergency flashers may provide a visual alert and a vehicle horn 78 and/or speaker 80 may provide an audible alert. Additionally, the controller 38 and/or vehicle alert system 74 may communicate with a human machine interface (HMI) 82 of the vehicle 12. The HMI 82 may include a touchscreen vehicle display 84 such as a center-stack mounted navigation or entertainment display capable of displaying images indicating the alert. Such an embodiment may be desirable to notify the driver of the vehicle 12 that an unacceptable trailer backup condition is afoot. Further, it is contemplated that the controller 38 may communicate via wireless communication with one or more electronic portable devices such as portable electronic device 86, which is embodied as a smartphone. The portable electronic device 86 may include a display 88 for displaying one or more images and other information to a user. In response, the portable electronic device 86 may provide feedback information, such as visual, audible, and tactile alerts.
When the imaging device 34 is installed on the vehicle 12, it is important to minimize errors arising during installation or at a later time. Such errors generally result from improper alignment between the imaging device 34 and the vehicle 12 in terms of yaw, pitch, and roll. These errors may be caused by various factors such as manufacturing variability, part-to-part variability over time, damage to the vehicle, or parts replacement, for example, all of which have the potential of changing the alignment between the imaging device 34 and the vehicle 12. Initially, these errors are calibrated before the imaging device 34 can be used to support functions such as imager-based hitch angle detection. If not properly calibrated, the resultant errors may negatively impact the accuracy and robustness of functions instituted by the imaging device 34.
Referring to
At step 95, a benchmark installation is prepared. For example, the benchmark installation includes positioning the imaging device in the ideal orientation relative to the vehicle. In the embodiment of
At step 105, edge detection is conducted on the captured image. For purposes of illustration,
In contrast, steps 120-150 are generally conducted on the assembly line and are repeated for each vehicle of the same model. For purposes of understanding, steps 120-150 will be described with respect to the embodiment of vehicle 12 shown in
Alternatively, if the position of the identified boundary fails to overlap with the position of the stored ideal boundary 111, the controller 38 determines an offset between the identified boundary and the stored ideal boundary 111 at step 145. For purposes of illustration,
It should be appreciated that the imaging device 34 may be calibrated multiple times during the life of the vehicle 12. For example, it is contemplated that the foregoing steps may be executed at regular time intervals, once per ignition cycle, if replacement of the imaging device 34 is detected, and/or if a collision is detected. It is further contemplated that the controller 38 may inhibit calibration of the imaging device 34 in instances where the orientation and/or position of the rear bumper 96 have changed substantially, the shape of the identified boundary 146 is unable to be matched to the stored ideal boundary 111 (typically due to damage or modification of the rear bumper 96), the rear bumper 96 is not securely attached to the vehicle 12, or the imaging device 34 is not securely fixed to the vehicle 12 (e.g., the tailgate 35 is not secure), for example. Additionally or alternatively, the calibration of the imaging device 34 may be inhibited if the values of components X, Y, and 0 exceed a predetermined threshold(s) or if the error between pixels of the boundary and the identified boundary exceed a threshold.
In the event the controller 38 inhibits calibration of the imaging device 34, a warning may be provided to a user of the TBA system 10. The warning may be generated by the controller 38 and carried out by existing vehicle components such as the display 34, speaker 80, for example, as well as portable electronic device 86. It is contemplated that the warning may be visual, auditory, haptic, or a combination thereof. In instances where damage to the vehicle 12 is detected (e.g., via inertial and/or perimeter sensors), the TBA system 10 may store a corresponding Diagnostic Trouble Code (DTC) and/or warn the user that the imaging device 34 and/or rear bumper 96 may require repair.
As described herein, the TBA system 10 features imager-based hitch angle detection, among other things. As a downside, there are instances where the imaging device 34 may be obstructed from tracking the trailer 14 or other objects in the imaged scene useful for hitch angle detection. For example, obstruction may occur when debris or other objects are deposited on the lens of the imaging device 34, the imaging device 34 experiences glare due to direct impingement of sunlight, or is unable to reliably image key features in the scene. In such instances where the imaging device 34 becomes obstructed, it is contemplated that the TBA system 10 may report the condition to the driver and may additionally cease imager-based hitch angle detection along with any other functions that rely on the processing of image data. While such instances are generally infrequent, the driver may become frustrated nonetheless if certain functions of the TBA system 10 become unavailable. Accordingly, a solution is needed that minimizes the downtime of image-based hitch angle detection due to the inability of the imaging device 34 to reliably image the scene.
In such a situation, the TBA system 10 may be configured to predict hitch angles using a “predictive model method,” which may be embodied in the hitch angle detection routine 44 and will be described in greater detail below with reference to
where:
γ is the hitch angle (β−α) between the vehicle 12 and the trailer 14,
δ is the steering angle of steered wheels 60 of the vehicle 12,
L is the drawbar length between the hitch 32 and a rear axle 155 of the vehicle 12,
D is the trailer length between the hitch 32 and effective axle 20 of the trailer 14,
W is the wheelbase length between a front axle 157 and the rear axle 155 of the vehicle 12, and
ν is the longitudinal speed of the vehicle 12. It is to be noted that the function
tan δ corresponds to the yaw rate of the vehicle 12 and can be otherwise supplied by vehicle yaw rate sensor 52 (
In calculating the angular velocity {dot over (γ)} of the trailer 14, it is assumed that the trailer length D, drawbar length L, and wheelbase length W are known. The steering angle δ and the longitudinal speed ν may be readily provided to the controller 38 by steering angle sensor 64 (
However, if the imaging device 34 suddenly becomes obstructed such that imager-based hitch angle detection becomes unavailable, the controller 38 can predict the hitch angle based on predetermined information including a last known hitch angle, a last known angular velocity of the trailer 14, and an execution cycle time of the image processor (e.g., microprocessor 40,
γp=γlk+{dot over (γ)}lktc (2)
where:
γp is a predicted hitch angle,
γlk is the last known hitch angle,
{dot over (γ)}lk is the last known angular velocity of the trailer 14, and
tc is the execution cycle time of the image processor. Thus, so long as the controller 38 is able to iterate equation 1 at least once before the imaging device 34 becomes obstructed, the controller 38 will have sufficient information to predict the hitch angle γp by iterating equation 2. The controller 38 may again calculate the angular velocity {dot over (γ)} of the trailer 14 by substituting the predicted hitch angle γp into equation 1, followed in turn by again predicting the hitch angle γp using the recalculated angular velocity {dot over (γ)} as the last known angular velocity {dot over (γ)}lk in equation 2. Thus, through stepwise reiteration of equations 1 and 2, the controller 38 is able predict the hitch angle in instances where imager-based hitch detection is unavailable or otherwise unreliable.
The predictive model method outlined above may be implemented for extended durations. However, as time progresses, the predicted hitch angle may begin to deviate from the true or actual hitch angle. Referring to
The degree error between the predicted hitch angle and the true hitch angle is determined by the following equation:
where:
e is the degree error,
e0 is an initial degree error at the moment the imaging device 34 becomes obstructed (e.g., 0.5 to 1 degree depending on the accuracy of hitch angle detection),
s is an accumulative vehicle travel distance determined by an odometer of the vehicle 12, and
D is the trailer length, which is assumed to be known.
Knowing the degree error e, the error band is determined by the following equations:
γ+=γp+e (4)
γ−=γp−e (5)
where:
γ+ is the upper error band,
γ− is the lower error band,
γp is the predicted hitch angle determined from equation 2, and
e is the degree error determined from equation 3. Alternatively, the determination of the upper and lower error bands may include an error adjustment incorporated into each iteration of equation 1. That is, the angular velocity {dot over (γ)} determined using equation 1 is adjusted by a percentage error and the adjusted angular velocity is then used as the last known angular velocity {dot over (γ)}lk when predicting the hitch angle γp in equation 2.
Specifically, with respect to the upper error band γ+, the adjustment made to the angular velocity {dot over (γ)} is given by the following equation:
{dot over (γ)}adj={dot over (γ)}+|{dot over (γ)}ε| (6)
With respect to the lower error band γ−, the adjustment made to the angular velocity {dot over (γ)} is given by the following equation:
{dot over (γ)}adj={dot over (γ)}−|{dot over (γ)}ε| (7)
where:
{dot over (γ)}adj is an adjusted angular velocity,
{dot over (γ)} is the angular velocity determined in equation 1, and
ε is a percentage error and is derived through experimentation. Accordingly, from equations 6 and 7, it can be seen that the adjusted angular velocity {dot over (γ)}adj associated with the upper and lower error bands will differ and therefore produce different predicted hitch angles γp when used as the last known angular velocity {dot over (γ)}lk in equation 2. Thus, equation 2 is iterated twice, once using the adjusted angular velocity {dot over (γ)}adj determined in equation 6, and a second time using the adjusted angular velocity {dot over (γ)}adj determined in equation 7. Each of the resulting predicted hitch angles γp is then used in the corresponding equation 4, 5 to determine the upper error band γ+ and the lower error band γ−, respectively.
In the event the upper error band γ+ approaches or reaches the maximum controllable hitch angle or the lower error band γ− reaches the minimum controllable hitch angle, the controller 38 may enact a countermeasure. For example the countermeasure may include providing steering commands to the power assist steering system 57 (
In the present embodiment, the controller 38 implements error band determination and functions both as an image processor and steering controller. In alternative embodiments where the image processor and steering controller are separate, it is contemplated that error band determination may be implemented by the image processor, steering controller, or a combination thereof. Generally, if the image processor and steering controller are together used to implement error band determination, additional traffic on the vehicle communication network (e.g., CAN bus) can be avoided at the expense of requiring additional hardware. If error band determination is only implemented using the steering controller, greater accuracy can be achieved at the expense of increased traffic on the vehicle communication network. Alternatively, if error band determination is only implemented using the image processor, additional traffic on the vehicle communication network can be avoided at the expense of accuracy. In instances where only one of the image processor and the steering controller is used to implement error band determination, a copy of the same may be supplied to the other of the image processor and the steering controller. Typically it is preferable to implement error band determination using both the image processor and the steering controller when there is no network interface (e.g., CAN interface) to accommodate the transmission of error band signals.
It is to be understood that the predictive model method described herein can be used to mitigate failure in other devices configured to sense the trailer 14. Such devices may include yaw rate sensors, Hall effect sensors, rotational potentiometers, and the like. In operation, data from these devices may be used by a controller to predict the hitch angle between a vehicle and a trailer. Accordingly, if one of these devices becomes unavailable, through failure or some other factor, the predictive model method may be used to determine the hitch angle.
Referring to
At step 175, the controller 38 uses the selected at least one hitch angle detection method to determine a hitch angle between a vehicle 12 and a trailer 14. In determining the hitch angle, other related data may become available such as, but not limited to, hitch angle error band, hitch angle rate, hitch angle rate error band, hitch angle accuracy, etc. According to one embodiment, it is contemplated that all of the hitch angle detection methods may be used in parallel to determine the hitch angle and the hitch angle determined by the hitch angle detection method having the highest confidence score is used by the TBA system 10 to employ functions related to the backing of the trailer 14. In other embodiments, only the hitch angle detection method having the highest confidence score is used. Alternatively, some, but not all, of the hitch angle detection methods may be used in parallel, if desired. In any event, it is contemplated that the number of selected hitch angle detection methods may be limited by the hardware capabilities of the TBA system 10 or certain components thereof (e.g., the imaging device 34 and controller 38). As such, the number of hitch angle detection methods used in parallel may be selected so as to minimize computational strain on the TBA system 10 and/or related components. Furthermore, it is contemplated that the controller 38 may limit the speed of the vehicle 12 based on the confidence score assigned to the at least one selected hitch angle detection method. That is, the lower the confidence score, the greater the speed restriction imposed on the vehicle 12. To limit the speed of the vehicle 12, the controller 38 may output a brake command to the vehicle brake control system 70 of the vehicle 12.
At step 180, the controller 38 transitions to another hitch angle detection method if the selected at least one hitch angle detection method becomes unavailable. As described herein, imager-based hitch angle detection is reliant on the ability of the imaging device 34 to accurately capture images of a rear-vehicle scene and typically including the trailer 14 or components thereof. As such, when the imaging device 34 is obstructed by debris on the lens, glare from the sun, etc., the image quality of the images captured by the imaging device 34 may suffer. Accordingly, there may be instances where some hitch angle detection methods are available and others become unavailable.
The controller 38 may determine that a particular hitch angle detection method becomes unavailable if the image quality of the captured images falls below a threshold associated with the particular hitch angle detection method. Thus, in embodiments where only the hitch angle detection method having the highest confidence score is used and suddenly becomes unavailable, the controller 38 may transition to another hitch angle detection method that is available and has the next highest confidence score. In embodiments where some, but not all, of the hitch angle detection methods are used in parallel, if one of the selected hitch angle detection methods suddenly becomes unavailable, the controller 38 may replace it with another hitch angle detection method that is available and has the highest confidence score amongst the unselected hitch angle detection methods. In this manner, the total selected hitch angle detection methods in use remains the same. By using more than one hitch angle detection method, the hitch angle may be determined at greater intervals since it is possible that each selected hitch angle detection method may require a certain period of time in which to determine the hitch angle. Thus, by increasing the number of hitch angle detection methods in use, the likelihood that a hitch angle can be determined at any given point in time is increased.
At step 185, the controller 38 predicts the hitch angle during the transitioning between the at least one selected hitch angle detection method and another hitch angle detection method or if each of the plurality of hitch angle detection methods become unavailable. To predict the hitch angle, the controller 38 may use the predictive model method described previously herein. Regardless of which method(s) is used to determine the hitch angle, the controller 38 may apply a digital filter to the determined hitch angle and other trailer related data in some embodiments. At step 190, the controller 38 uses the determined or predicted hitch angle to control at least one of a hitch angle operating range, a speed limit of the vehicle 12, and the desired curvature 56 (
Existing TBA systems may employ a curvature routine that requires an operator to measure the trailer length D for input into system memory. Such systems exhibit certain drawbacks, such as the introduction of human error and/or the inability for the TBA system to operate immediately upon connecting, for example, trailer 14 with vehicle 12. Accordingly, the present controller 38 may incorporate a yaw-rate based routine embodied in the curvature routine 47 (
As shown in
Referring to
Φ(δmaxb, {circumflex over (D)}) corresponds to an effective jackknife angle {circumflex over (γ)}jk and is provided by the following equation:
where:
δmaxb is a constant defined by a maximum steering angle δmax less a configurable buffer Δbuf, where Δbuf≥0,
{circumflex over (D)} is an estimated trailer length,
L is the drawbar length and is assumed to be known, and
W is the vehicle wheelbase and is assumed to be known. The effective jackknife angle {circumflex over (γ)}jk may be less than a theoretical jackknife angle, since in practice, the controller 38 may generate some overshoot in hitch angle, and it is generally desirable to retain additional steering lock to ensure quick transitioning from maximum curvature to zero curvature.
Γ({circumflex over (γ)}jk, {circumflex over (D)}) corresponds to the maximum effective curvature {circumflex over (k)}2max and is provided by the following equation:
where:
{circumflex over (γ)}jk is the effective jackknife angle determined by equation 8,
L is the drawbar length, and
{circumflex over (D)} is the estimated trailer length. With respect to this disclosure, the curvature input scaling module 200, as defined by the sequential input-output of the composition Φ(δmaxb, {circumflex over (D)})∘Γ({circumflex over (γ)}jk, {circumflex over (D)})·k(t), is denoted by K(k(t), δmaxb, {circumflex over (D)}) for purposes of simplicity.
With reference to
where:
{circumflex over (k)}2(t) is the curvature input,
L is the drawbar length, and
{circumflex over (D)} is the estimated trailer length.
The reference hitch angle {circumflex over (γ)}ref(t), as provided by the curvature mapping module 204, and the estimated hitch angle {circumflex over (γ)}(t), as provided by the estimator 202, are received by a subtractor 206 configured to generate a signal e(t) defined by the reference hitch angle {circumflex over (γ)}ref(t) less the estimated hitch angle {circumflex over (γ)}(t). The estimated hitch angle {circumflex over (γ)}(t) is provided by the following equation:
where:
ω1(t) is the vehicle yaw rate,
ω2(t) is the trailer yaw rate,
L is the drawbar length,
{circumflex over (D)} is the estimated trailer length, and
ν(t) is vehicle speed. In real-time implementation, a Kalman filter may be used with the estimated hitch angle {circumflex over (γ)}(t) along with an internal state measurement thereof.
The signal e(t) is provided to a proportional-integral (PI) controller 208 to generate a control variable u(t) defined by the following equation:
u(t)=Kpe(t)+Ki∫0te(τ)dτ, (12)
where:
e(t) is the signal generated by the subtractor 206,
Kp is a proportional coefficient having a non-negative value, and
Ki is an integral coefficient having a non-negative value.
The control variable u(t) is provided to a hitch angle controller 210 along with the estimated trailer length {circumflex over (D)} and the estimated hitch angle {circumflex over (γ)}(t), as provided by the estimator 202, and a vehicle speed υ(t), as provided by speed sensor 50 (
where:
u(t) is the control variable generated by the PI controller 208,
{circumflex over (D)} is the estimated trailer length,
{circumflex over (γ)}(t) is the estimated hitch angle provided by the estimator 202,
W is the vehicle wheelbase,
{circumflex over (D)} is the estimated trailer length, and
υ(t) is the vehicle speed as provided by speed sensor 50 (
When the controller 38 is configured according to the embodiment shown in
In this manner, the closed-loop dynamics are shaped in a uniform manner.
It is to be understood that variations and modifications can be made on the aforementioned structures and methods without departing from the concepts of the present invention, and further it is to be understood that such concepts are intended to be covered by the following claims unless these claims by their language expressly state otherwise.