The disclosure made herein relates generally to driver assist and active safety technologies in vehicles, and more particularly to methods of determining a trailer length that may be used in conjunction with a trailer backup assist system.
Reversing a vehicle while towing a trailer is very challenging for many drivers. This is particularly true for drivers that are unskilled at backing vehicles with attached trailers, which may include those that drive with a trailer on an infrequent basis (e.g., have rented a trailer, use a personal trailer on an infrequent basis, etc.). One reason for such difficulty is that backing a vehicle with an attached trailer requires steering inputs that are opposite to normal steering when backing the vehicle without a trailer attached and/or requires braking to stabilize the vehicle-trailer combination before a jackknife condition occurs. Another reason for such difficulty is that small errors in steering while backing a vehicle with an attached trailer are amplified thereby causing the trailer to depart from a desired path.
To assist the driver in steering a vehicle with a trailer attached, a trailer backup assist system needs to know the driver's intention. One common assumption with known trailer backup assist systems is that a driver of a vehicle with an attached trailer wants to backup straight and the system either implicitly or explicitly assumes a zero curvature path for the vehicle-trailer combination. Unfortunately most of the real-world use cases of backing a trailer involve a curved path and, thus, assuming a path of zero curvature would significantly limit usefulness of the system. Some known systems assume that a path is known from a map or path planner. To this end, some known trailer backup assist systems operate under a requirement that a trailer backup path is known before backing of the trailer commences such as, for example, from a map or a path-planning algorithm. Undesirably, such implementations of the trailer backup assist systems are known to have a relatively complex human machine interface (HMI) device to specify the path, obstacles and/or goal of the backup maneuver. Furthermore, such systems also require some way to determine how well the desired path is being followed and to know when the desired goal, or stopping point and orientation, has been met, using approaches such as cameras, inertial navigation, or high precision global positioning system (GPS). These requirements lead to a relatively complex and costly system.
Another reason backing a trailer can prove to be difficult is the need to control the vehicle in a manner that limits the potential for a jackknife condition to occur. A trailer has attained a jackknife condition when a hitch angle cannot be reduced (i.e., made less acute) while continuously backing up a trailer by application of a maximum steering input for the vehicle such as, for example, by moving steered front wheels of the vehicle to a maximum steered angle at a maximum rate of steering angle change. In the case of the jackknife angle being achieved, the vehicle must be pulled forward to relieve the hitch angle in order to eliminate the jackknife condition and, thus, allow the hitch angle to be controlled via manipulation of the steered wheels of the vehicle. However, in addition to the jackknife condition creating the inconvenient situation where the vehicle must be pulled forward, it can also lead to damage to the vehicle and/or trailer if certain operating conditions of the vehicle relating to its speed, engine torque, acceleration, and the like are not detected and counteracted. For example, if the vehicle is travelling at a suitably high speed in reverse and/or subjected to a suitably high longitudinal acceleration when the jackknife condition is achieved, the relative movement of the vehicle with respect to the trailer can lead to contact between the vehicle and trailer thereby damaging the trailer and/or the vehicle.
According to one aspect of the present invention, a device is disclosed for estimating a trailer length. The device includes a processor in communication with a wheel steer angle sensor and a hitch angle sensor. The processor is operable to determine a wheel steer angle change and a hitch angle change and perform a first computation if the wheel steer angle change and the hitch angle change are each within a predetermined range.
According to another aspect of the present invention, a vehicle system for estimating a trailer length is disclosed. The vehicle system includes a first sensor for measuring a wheel steer angle and a second sensor for measuring a hitch angle. A processor is in communication with the first and second sensors and is operable to determine a wheel steer angle change and a hitch angle change. The processor performs a first computation if the wheel steer angle change and the hitch angle change satisfy a threshold requirement and performs a second computation if at least one of the wheel steer angle change and the hitch angle change does not satisfy the threshold requirement.
According to a further aspect of the present invention, a trailer length estimation method is disclosed. The method includes the step of sampling a wheel steer angle and a hitch angle to determine a wheel steer angle change and a hitch angle change. The method also includes the step of determining if the wheel steer angle change and the hitch angle change satisfy a threshold requirement. The method further includes the step of performing a first computation if the threshold requirement is satisfied and performing a second computation if the threshold requirement is not satisfied.
These and other aspects, objects, and features of the present invention will be understood and appreciated by those skilled in the art upon studying the following specification, claims, and appended drawings.
In the drawings:
While various aspects of the inventive subject matter are described with reference to a particular illustrative embodiment, the inventive subject matter is not limited to such embodiments, and additional modifications, applications, and embodiments may be implemented without departing from the inventive subject matter. In the figures, like reference numbers will be used to illustrate the same components. Those skilled in the art will recognize that the various components set forth herein may be altered without varying from the scope of the inventive subject matter.
Trailer Backup Assist System
Referring to
The trailer backup assist system 105 includes a trailer backup assist control module 120, a trailer backup steering input apparatus 125, and a hitch angle detection apparatus 130. The trailer backup assist control module 120 is connected to the trailer backup steering input apparatus 125 and the hitch angle detection apparatus 130 for allowing communication of information therebetween. It is disclosed herein that the trailer backup steering input apparatus can be coupled to the trailer backup assist control module 120 in a wired or wireless manner. The trailer backup assist system control module 120 is attached to a power steering assist control module 135 of the power steering assist system 115 for allowing information to be communicated therebetween. A steering angle detection apparatus 140 of the power steering assist system 115 is connected to the power steering assist control module 135 for providing information thereto. The trailer backup assist system is also attached to a brake system control module 145 and a powertrain control module 150 for allowing communication of information therebetween. Jointly, the trailer backup assist system 105, the power steering assist system 115, the brake system control module 145, the powertrain control module 150, and the gear selection device (PRNDL), define a trailer backup assist architecture configured in accordance with an embodiment.
The trailer backup assist control module 120 is configured for implementing logic (i.e., instructions) for receiving information from the trailer backup steering input apparatus 125, the hitch angle detection apparatus 130, the power steering assist control module 135, the brake system control module 145, and the powertrain control module 150. The trailer backup assist control module 120 (e.g., a trailer curvature algorithm thereof) generates vehicle steering information as a function of all or a portion of the information received from the trailer backup steering input apparatus 125, the hitch angle detection apparatus 130, the power steering assist control module 135, the brake system control module 145, and the powertrain control module 150. Thereafter, the vehicle steering information is provided to the power steering assist control module 135 for affecting steering of the vehicle 100 by the power steering assist system 115 to achieve a commanded path of travel for the trailer 110.
The trailer backup steering input apparatus 125 provides the trailer backup assist control module 120 with information defining the commanded path of travel of the trailer 110 to the trailer backup assist control module 120 (i.e., trailer steering information). The trailer steering information can include information relating to a commanded change in the path of travel (e.g., a change in radius of path curvature) and information relating to an indication that the trailer is to travel along a path defined by a longitudinal centerline axis of the trailer (i.e., along a substantially straight path of travel). As will be discussed below in detail, the trailer backup steering input apparatus 125 preferably includes a rotational control input device for allowing a driver of the vehicle 100 to interface with the trailer backup steering input apparatus 125 to command desired trailer steering actions (e.g., commanding a desired change in radius of the path of travel of the trailer and/or commanding that the trailer travel along a substantially straight path of travel as defined by a longitudinal centerline axis of the trailer). In a preferred embodiment, the rotational control input device is a knob rotatable about a rotational axis extending through a top surface/face of the knob. In other embodiments, the rotational control input device is a knob rotatable about a rotational axis extending substantially parallel to a top surface/face of the knob.
Some vehicles (e.g., those with active front steer) have a power steering assist system configuration that allows a steering wheel to be partially decoupled from movement of the steered wheels of such a vehicle. Accordingly, the steering wheel can be rotated independent of the manner in which the power steering assist system of the vehicle controls the steered wheels (e.g., as commanded by vehicle steering information provided by a power steering assist system control module from a trailer backup assist system control module configured in accordance with one embodiment). As such, in these types of vehicles where the steering wheel can be selectively decoupled from the steered wheels to allow independent operation thereof, trailer steering information of a trailer backup assist system configured in accordance with the disclosed subject matter can be provided through rotation of the steering wheel. Accordingly, it is disclosed herein that in certain embodiments, the steering wheel is an embodiment of a rotational control input device in the context of the disclosed subject matter. In such embodiments, the steering wheel would be biased (e.g., by an apparatus that is selectively engageable/activatable) to an at-rest position between opposing rotational ranges of motion.
The hitch angle detection apparatus 130, which operates in conjunction with a hitch angle detection component 155 of the trailer 110, provides the trailer backup assist control module 120 with information relating to an angle between the vehicle 100 and the trailer 110 (i.e., hitch angle information). In a preferred embodiment, the hitch angle detection apparatus 130 is a camera-based apparatus such as, for example, an existing rear view camera of the vehicle 100 that images (i.e., visually monitors) a target (i.e., the hitch angle detection component 155) attached the trailer 110 as the trailer 110 is being backed by the vehicle 100. Preferably, but not necessarily, the hitch angle detection component 155 is a dedicated component (e.g., an item attached to/integral with a surface of the trailer 110 for the express purpose of being recognized by the hitch angle detection apparatus 130). Alternatively, the hitch angle detection apparatus 130 can be a device that is physically mounted on a hitch component of the vehicle 100 and/or a mating hitch component of the trailer 110 for determining an angle between centerline longitudinal axes of the vehicle 100 and the trailer 110. The hitch angle detection apparatus 130 can be configured for detecting a jackknife enabling condition and/or related information (e.g., when a hitch angle threshold has been met).
The power steering assist control module 135 provides the trailer backup assist control module 120 with information relating to a rotational position (e.g., angle) of the wheel steer angle and/or a rotational position (e.g., turning angle(s)) of steered wheels of the vehicle 100. In certain embodiments, the trailer backup assist control module 120 can be an integrated component of the power steering assist system 115. For example, the power steering assist control module 135 can include a trailer backup assist algorithm for generating vehicle steering information as a function of all or a portion of information received from the trailer backup steering input apparatus 125, the hitch angle detection apparatus 130, the power steering assist control module 135, the brake system control module 145, and the powertrain control module 150.
The brake system control module 145 provides the trailer backup assist control module 120 with information relating to vehicle speed. Such vehicle speed information can be determined from individual wheel speeds as monitored by the brake system control module 145 or may be provided by an engine control module with signal plausibility. Vehicle speed may also be determined from an engine control module. In some instances, individual wheel speeds can also be used to determine a vehicle yaw rate and such yaw rate can be provided to the trailer backup assist control module 120 for use in determining the vehicle steering information. In certain embodiments, the trailer backup assist control module 120 can provide vehicle braking information to the brake system control module 145 for allowing the trailer backup assist control module 120 to control braking of the vehicle 100 during backing of the trailer 110. For example, using the trailer backup assist control module 120 to regulate speed of the vehicle 100 during backing of the trailer 110 can reduce the potential for unacceptable trailer backup conditions. Examples of unacceptable trailer backup conditions include, but are not limited to, a vehicle over speed condition, a high hitch angle rate, trailer angle dynamic instability, a calculated theoretical trailer jackknife condition (defined by a maximum vehicle steering angle, drawbar length, tow vehicle wheelbase and an effective trailer length), or physical contact jackknife limitation (defined by an angular displacement limit relative to the vehicle 100 and the trailer 110), and the like. It is disclosed herein that the backup assist control module 120 can issue a signal corresponding to a notification (e.g., a warning) of an actual, impending, and/or anticipated unacceptable trailer backup condition.
The powertrain control module 150 interacts with the trailer backup assist control module 120 for regulating speed and acceleration of the vehicle 100 during backing of the trailer 110. As mentioned above, regulation of the speed of the vehicle 100 is necessary to limit the potential for unacceptable trailer backup conditions such as, for example, jackknifing and trailer angle dynamic instability. Similar to high-speed considerations as they relate to unacceptable trailer backup conditions, high acceleration and high dynamic driver curvature requests can also lead to such unacceptable trailer backup conditions.
Steering Input Apparatus
Referring now to
The movement sensing device 175 is configured for sensing movement of the knob 170 and outputting a corresponding signal (i.e., movement sensing device signal) to the trailer assist backup input apparatus 125 shown in
Use of the knob 170 decouples trailer steering inputs from being made at a steering wheel of the vehicle 100. In use, as a driver of the vehicle 100 backs the trailer 110, the driver can turn the knob 170 to indicate a desired curvature of a path of the trailer 110 to follow and returns the knob 170 to the at-rest position P(AR) for causing the trailer 110 to be backed along a straight line. Accordingly, in embodiments of trailer backup assist systems where the steering wheel remains physically coupled to the steerable wheels of a vehicle during backup of an attached trailer, a rotatable control element configured in accordance with the disclosed subject matter (e.g., the knob 170) provides a simple and user-friendly means of allowing a driver of a vehicle to input trailer steering commands.
It is disclosed herein that a rotational control input device configured in accordance with embodiments of the disclosed subject matter (e.g., the knob 170 and associated movement sensing device) can omit a means for being biased to an at-rest position between opposing rotational ranges of motion. Lack of such biasing allows a current rotational position of the rotational control input device to be maintained until the rotational control input device is manually moved to a different position. Preferably, but not necessarily, when such biasing is omitted, a means is provided for indicating that the rotational control input device is positioned in a zero curvature commanding position (e.g., at the same position as the at-rest position in embodiments where the rotational control input device is biased). Examples of means for indicating that the rotational control input device is positioned in the zero curvature commanding position include, but are not limited to, a detent that the rotational control input device engages when in the zero curvature commanding position, a visual marking indicating that the rotational control input device is in the zero curvature commanding position, an active vibratory signal indicating that the rotational control input device is in or approaching the zero curvature commanding position, an audible message indicating that the rotational control input device is in of approaching the zero curvature commanding position, and the like.
It is also disclosed herein that embodiments of the disclosed subject matter can be configured with a control input device that is not rotational (i.e., a non-rotational control input device). Similar to a rotational control input device configured in accordance with embodiments of the disclosed subject matter (e.g., the knob 170 and associated movement sensing device), such a non-rotational control input device is configured to selectively provide a signal causing a trailer to follow a path of travel segment that is substantially straight and to selectively provide a signal causing the trailer to follow a path of travel segment that is substantially curved. Examples of such a non-rotational control input device include, but are not limited to, a plurality of depressible buttons (e.g., curve left, curve right, and travel straight), a touch screen on which a driver traces or otherwise inputs a curvature for path of travel commands, a button that is translatable along an axis for allowing a driver to input path of travel commands, or joystick type input and the like.
The trailer backup steering input apparatus 125 can be configured to provide feedback information to a driver of the vehicle 100. Examples of situation that such feedback information can include, but are not limited to, a status of the trailer backup assist system 105 (e.g., active, in standby (e.g., when driving forward to reduce the hitch angle and zero hitch angle to remove bias), faulted, inactive, etc.), that a curvature limit has been reached (i.e., maximum commanded curvature of a path of travel of the trailer 110), and/or a graphical representation of the vehicle and trailer orientation state. To this end, the trailer backup steering input apparatus 125 can be configured to provide a tactile feedback signal (e.g., a vibration through the knob 170) as a warning if any one of a variety of conditions occur. Examples of such conditions include, but are not limited to, the trailer 110 approaching jackknife, the trailer backup assist system 105 has had a failure, the trailer backup assist system 105 has detected a fault, the trailer backup assist system 105 or other system of the vehicle 100 has predicted a collision on the present path of travel of the trailer 110, the trailer backup system 105 has restricted a commanded curvature of a trailer's path of travel (e.g., due to excessive speed or acceleration of the vehicle 100), and the like. Still further, it is disclosed that the trailer backup steering input apparatus 125 can use illumination (e.g., an LED 180) and/or an audible signal output (e.g., an audible output device 185 or through attached vehicle audio speakers) to provide certain feedback information (e.g., notification/warning of an unacceptable trailer backup condition).
Referring now to
After activating the trailer backup assist system 105 (e.g., before, after, or during the pull-thru sequence), the driver begins to back the trailer 110 by reversing the vehicle 100 from the first backup position B1. So long as the knob 170 of the trailer backup steering input apparatus 125 remains in the at-rest position P(AR), the trailer backup assist system 105 will steer the vehicle 100 as necessary for causing the trailer 110 to be backed along a substantially straight path of travel as defined by the longitudinal centerline axis L2 of the trailer 110 at the time when backing of the trailer 110 began. When the trailer reaches the second backup position B2, the driver rotates the knob 170 to command the trailer 110 to be steered to the right (i.e., a knob position R(R) clockwise rotation). Accordingly, the trailer backup assist system 105 will steer the vehicle 100 for causing the trailer 110 to be steered to the right as a function of an amount of rotation of the knob 170 with respect to the at-rest position P(AR), a rate movement of the knob 170, and/or a direction of movement of the knob 170 with respect to the at-rest position P(AR). Similarly, the trailer 110 can be commanded to steer to the left by rotating the knob 170 to the left. When the trailer reaches backup position B3, the driver allows the knob 170 to return to the at-rest position P(AR) thereby causing the trailer backup assist system 105 to steer the vehicle 100 as necessary for causing the trailer 110 to be backed along a substantially straight path of travel as defined by the longitudinal centerline axis L2 of the trailer 110 at the time when the knob 170 was returned to the at-rest position P(AR). Thereafter, the trailer backup assist system 105 steers the vehicle 100 as necessary for causing the trailer 110 to be backed along this substantially straight path to the fourth backup position B4. In this regard, arcuate portions of a path of travel POT of the trailer 110 are dictated by rotation of the knob 170 and straight portions of the path of travel POT are dictated by an orientation of the centerline longitudinal axis L2 of the trailer when the knob 170 is in/returned to the at-rest position P(AR).
In order to activate the trailer backup assist system described above in
An operation 202 is performed for receiving a trailer backup assist request. Examples of receiving the trailer backup assist request include activating the trailer backup assist system and providing confirmation that the vehicle and trailer are ready to be backed. After receiving a trailer backup assist request (i.e., while the vehicle is being reversed), an operation 204 is performed for receiving a trailer backup information signal. Examples of information carried by the trailer backup information signal include, but are not limited to, information from the trailer backup steering input apparatus 125, information from the hitch angle detection apparatus 130, information from the power steering assist control module 135, information from the brake system control module 145, and information from the powertrain control module 150. It is disclosed herein that information from the trailer backup steering input apparatus 125 preferably includes trailer path curvature information characterizing a desired curvature for the path of travel of the trailer, such as provided by the trailer backup steering input apparatus 125 discussed above in reference to
If the trailer backup information signal indicates that a change in curvature of the trailer's path of travel is requested (i.e., commanded via the knob 170), an operation 206 is performed for determining vehicle steering information for providing the requested change in curvature of the trailer's path of travel. Otherwise, an operation 208 is performed for determining vehicle steering information for maintaining a current straight-line heading of the trailer (i.e., as defined by the longitudinal centerline axis of the trailer). Thereafter, an operation 210 is performed for providing the vehicle steering information to a power steering assist system of the vehicle, followed by an operation 212 being performed for determining the trailer backup assist status. If it is determined that trailer backup is complete, an operation 214 is performed for ending the current trailer backup assist instance. Otherwise the method 200 returns to the operation 204 for receiving trailer backup information. Preferably, the operation for receiving the trailer backup information signal, determining the vehicle steering information, providing the vehicle steering information, and determining the trailer backup assist status are performed in a monitoring fashion (e.g., at a high rate of speed of a digital data processing device). Accordingly, unless it is determined that reversing of the vehicle for backing the trailer is completed (e.g., due to the vehicle having been successfully backed to a desired location during a trailer backup assist instance, the vehicle having to be pulled forward to begin another trailer backup assist instance, etc.), the method 200 will continually be performing the operations for receiving the trailer backup information signal, determining the vehicle steering information, providing the vehicle steering information, and determining the trailer backup assist status.
It is disclosed herein that the operation 206 for determining vehicle steering information for providing the requested change in curvature of the trailer's path of travel preferably includes determining vehicle steering information as a function of trailer path curvature information contained within the trailer backup information signal. As will be discussed below in greater detail, determining vehicle steering information can be accomplished through a low order kinematic model defined by the vehicle and the trailer. Through such a model, a relationship between the trailer path curvature and commanded steering angles of steered wheels of the vehicle can be generated for determining steering angle changes of the steered wheels for achieving a specified trailer path curvature. In this manner, the operation 206 for determining vehicle steering information can be configured for generating information necessary for providing trailer path curvature control in accordance with the disclosed subject matter.
In some embodiments of the disclosed subject matter, the operation 210 for providing the vehicle steering information to the power steering assist system of the vehicle causes the steering system to generate a corresponding steering command as a function of the vehicle steering information. The steering command is interpretable by the steering system and is configured for causing the steering system to move steered wheels of the steering system for achieving a steered angle as specified by the vehicle steering information. Alternatively, the steering command can be generated by a controller, module or computer external to the steering system (e.g., a trailer backup assist control module) and be provided to the steering system.
In parallel with performing the operations for receiving the trailer backup information signal, determining the vehicle steering information, providing the vehicle steering information, and determining the trailer backup assist status, the method 200 performs an operation 216 for monitoring the trailer backup information for determining if an unacceptable trailer backup condition exists. Examples of such monitoring include, but are not limited to assessing a hitch angle to determine if a hitch angle threshold is exceeded, assessing a backup speed to determine if a backup speed threshold is exceeded, assessing vehicle steering angle to determine if a vehicle steering angle threshold is exceeded, assessing other operating parameters (e.g., vehicle longitudinal acceleration, throttle pedal demand rate and hitch angle rate) for determining if a respective threshold value is exceeded, and the like. Backup speed can be determined from wheel speed information obtained from one or more wheel speed sensors of the vehicle. If it is determined that an unacceptable trailer backup condition exists, an operation 218 is performed for causing the current path of travel of the trailer to be inhibited (e.g., stopping motion of the vehicle), followed by the operation 214 being performed for ending the current trailer backup assist instance. It is disclosed herein that prior to and/or in conjunction with causing the current trailer path to be inhibited, one or more actions (e.g., operations) can be implemented for providing the driver with feedback (e.g., a warning) that such an unacceptable hitch angle condition is impending or approaching. In one example, if such feedback results in the unacceptable hitch angle condition being remedied prior to achieving a critical condition, the method can continue with providing trailer backup assist functionality in accordance with operations 204-212. Otherwise, the method can proceed to operation 214 for ending the current trailer backup assist instance. In conjunction with performing the operation 214 for ending the current trailer backup assist instance, an operation can be performed for controlling movement of the vehicle to correct or limit a jackknife condition (e.g., steering the vehicle, decelerating the vehicle, limiting magnitude and/or rate of driver requested trailer curvature input, limiting magnitude and/or rate of the steering command, and/or the like to preclude the hitch angle from being exceeded).
Jackknife Detection
Referring to
Referring to
Solving the above equation for hitch angle allows jackknife angle γ(j) to be determined. This solution, which is shown in the following equation, can be used in implementing trailer backup assist functionality in accordance with the disclosed subject matter for monitoring hitch angle in relation to jackknife angle.
where,
a=L2 tan2 δ(max)+W2;
b=2LD tan2 δ(max);
and
c=D2 tan2 δ(max)−W2.
In certain instances of backing a trailer, a jackknife enabling condition can arise based on current operating parameters of a vehicle in combination with a corresponding hitch angle. This condition can be indicated when one or more specified vehicle operating thresholds are met while a particular hitch angle is present. For example, although the particular hitch angle is not currently at the jackknife angle for the vehicle and attached trailer, certain vehicle operating parameters can lead to a rapid (e.g., uncontrolled) transition of the hitch angle to the jackknife angle for a current commanded trailer path curvature and/or can reduce an ability to steer the trailer away from the jackknife angle. One reason for a jackknife enabling condition is that trailer curvature control mechanisms (e.g., those in accordance with the disclosed subject matter) generally calculate steering commands at an instantaneous point in time during backing of a trailer. However, these calculations will typically not account for lag in the steering control system of the vehicle (e.g., lag in a steering controller for an electric power assisted steering (EPAS) system). Another reason for the jackknife enabling condition is that trailer curvature control mechanisms generally exhibit reduced steering sensitivity and/or effectiveness when the vehicle is at relatively high speeds and/or when undergoing relatively high acceleration.
Human Machine Interface
In order to implement the method described in
The trailer backup assist system 105 will guide a driver through the steps necessary to connect a trailer and attach a target. The driver may activate the setup by way of the backup steering input apparatus 125, for example by turning or pushing the rotary knob, or my merely making a selection for the trailer backup assist system from a menu on the HMI device 102. Referring to
Once the system is selected by either the trailer backup steering input apparatus 125 or the HMI device 102, the system will guide the driver to prepare the vehicle and vehicle trailer combination as necessary. The vehicle 100 should be turned “on” and the vehicle 100 should be in “park” 590. In the event the vehicle 100 is on but is traveling at a speed that is greater than a predetermined limit, for example five miles per hour, the trailer backup assist system 105 will become inactive and inaccessible to the driver. The trailer backup assist system 105 setup module 600 will not begin or will be exited 585. If the type of trailer 110 selected by the driver is a trailer 110 that is not compatible with the trailer backup assist system 105, the setup module 600 will be exited 585 or will not begin. In the event, the trailer 110 is compatible with the trailer backup assist system 105, the setup module 600 verifies that the vehicle 100 gear shift mechanism is in “park.” Again, in the event the vehicle is not “on” and the gear shift mechanism is not on “park,” the setup module will not begin 585.
Upon connection 580 of a compatible trailer 110, the vehicle 100 being “on” 590 and the vehicle 100 being in “park” 590, the HMI 102 will present a menu 104 that has a “Towing” mode option to be selected by the driver. The driver selects “Towing” mode and a menu 104 is presented that provides a “Trailer Options” selection. The driver then selects a “Trailer Options” mode from the “Towing” menu. The driver is prompted to either “add a trailer” or “select a trailer” from a menu 104 presented on the HMI device and the “Setup” module 600 has begun. For certain camera-based hitch angle detection systems, an operation 602 is performed wherein a warning menu may be presented to the driver, by way of the HMI, informing the driver that the trailer must be in a straight line, meaning there is no angle at the hitch between the vehicle and the trailer. The warning indicates that the driver may need to take corrective action, for example, pull the vehicle forward in order to align the trailer and the vehicle as required for the setup 600. A generic or static graphic may be presented by way of the HMI 102 to assist the driver in visually recognizing the alignment between the trailer 110 and the vehicle 100 that is necessary in order to properly setup and calibrate the trailer backup assist system 105. The driver applies any corrections 603 in that the driver makes any necessary adjustment he has been alerted to and indicates, by acknowledging that corrective actions have been applied 603 and that the trailer is in line with the vehicle. Other hitch angle detection systems may not need the driver to straighten the trailer during setup mode.
To aid the driver in the setup process, the reverse back lights, or any other supplemental lighting that may be available on the vehicle, are illuminated 604. In the event the trailer is a new trailer, one that has not been attached to the vehicle before or has not been previously stored in the trailer backup assist system, the driver is presented 606 with an option to either name the trailer or select a previously stored trailer configuration. Naming the trailer 608 allows the trailer to be easily identified the next time it is attached to the vehicle so that the driver does not have to repeat the setup process. The driver either enters a unique name to identify the trailer that is to be stored in the trailer backup assist system or selects a previously stored trailer configuration associated with the attached trailer. The trailer backup assist system will not allow more than one trailer to have the same name. Therefore, if a driver attempts to name a trailer using a name that has already been applied to a previously stored trailer configuration, the HMI will display a message to the driver indicating so and requesting the driver enter a different name for the trailer configuration. In the case where a previously stored trailer configuration is available and selected 610 by the driver, certain steps in the setup process may be skipped.
The following discussion is directed to a first time trailer configuration for a camera-based hitch angle detection system. The driver is instructed 612 to place a hitch angle target on the trailer that is used for calibration purposes. A generic static image may be displayed on the HMI that provides direction to the driver as to placement of a target on the trailer that is used for hitch angle detection. The target placement is dependent upon the type of trailer being towed and therefore, options may be presented to the driver to aid the driver in selecting an appropriate trailer type. The static image may indicate areas that are acceptable for target placement as well as areas that are unacceptable for target placement. The static image indicating the appropriate areas for attaching the target may be an overlay of the rear view of the trailer hitch. Once the driver attaches the target to the trailer and indicates by way of the HMI that the target has been attached to the trailer, the setup mode provides 614 visual feedback to the driver identifying that the target has been located, or acquired. The driver acknowledges 616, by way of the HMI, that the target has been properly identified by the trailer backup assist system. Similarly, for a previously stored trailer configuration, the trailer will already have a target placed thereon. The trailer backup assist system will acquire the target and provide 614 visual feedback to the driver confirming acquisition of the target.
In the event the target is not acquired 614 after a predetermined amount of time lapses, the driver is notified 618 of the need to reposition the target and presented with possible corrective measures that may be taken. Possible corrective measures may be presented to the driver such as cleaning the camera lens, cleaning the target, replacing the target if it has been damaged or faded, pulling the vehicle-trailer combination forward to improve lighting conditions around the camera and/or target, and moving the target to an acceptable location. The driver applies the necessary corrections 603. As mentioned above, some hitch angle detection systems may not require the driver to attach a target to the trailer during set up mode. The target and acquisition of the target are directed to camera-based hitch angle detection systems.
When the target is acquired 614 by the trailer backup assist system and the driver has acknowledged 616 the acquisition, the driver is then prompted through a series of menus to input 620 trailer measurement information that may be stored in the trailer backup assist system for a trailer configuration that is to be associated with the named trailer. The next time the same trailer is attached to the vehicle, its unique trailer configuration will already be stored and progress through the setup module will be faster or, in some cases, may be skipped entirely. Generic static images may be displayed at the HMI screen in order to assist the driver with the measurement information. Visual examples, see
It should be noted that while measurement information is discussed above as being entered by the driver, various methods of entering measurement information may also be employed without departing from the scope of the disclosed subject matter. For example, a system to automatically detect measurements using existing vehicle and trailer data including, but not limited to, vehicle speed, wheel rotation, wheel steer angle, vehicle to trailer relative angle, and a rate of change of the vehicle to hitch angle.
Examples of the measurement information may include a horizontal distance from the rear of the vehicle to the center of a hitch ball, a horizontal distance from the rear of the vehicle to a center of the target, a vertical distance from the target to the ground, and a horizontal offset of the target from a centerline of the hitch ball. In the event the target is attached at other than the centerline of the hitch ball, then the trailer backup assist system must know which side of the vehicle the target is attached to, the passenger side or the driver side. A menu on the HMI may be presented for the driver to indicate passenger side or driver side for the placement of the target. The trailer backup assist system also needs to know the horizontal distance from the rear of the vehicle to a center of the axle or axles of the trailer. The measurements may be entered in either English or metric units.
The driver is presented 622 with the option to revise any of the measurements before proceeding with the setup process. Otherwise, the setup module 600 is complete 624 and the calibration module 700 begins.
The calibration module 700 is designed to calibrate the curvature control algorithm with the proper trailer measurements and calibrate the trailer backup assist system for any hitch angle offset that may be present. After completing the setup module 600, the calibration module begins 700 and the driver is instructed 702 to pull the vehicle-trailer combination straight forward until a hitch angle sensor calibration is complete. The HMI may notify 704 the driver, by way of a pop up or screen display that the vehicle-trailer combination needs to be pulled forward until calibration is complete. When calibration is complete, the HMI may notify 704 the driver. Any hitch angle offset value is stored 706 in memory, accessed as necessary by the curvature control algorithm, and the calibration module 700 ends 704.
It should be noted that while hitch angle calibration is described above as may be requesting the driver pull forward information, various other methods of hitch angle calibration may also be employed without departing from the scope of the embodiment.
Upon completion of the setup module 600 and the calibration module 700, the activation module 800 may begin. The activation module 800 is described with reference to
For steering systems where the steering wheel is directly coupled to the steered wheels of the vehicle, the driver cannot engage with the steering wheel during trailer backup assist. If any steering wheel motion is obstructed, by the driver or otherwise, the trailer backup assist system will present instructions 810 to the driver to remove their hands from the steering wheel. Activation 800 will be suspended or discontinued until the obstruction is removed. If the vehicle speed exceeds a threshold speed or if the vehicle hitch angle is not acceptable, the driver will be prompted 810 to take corrective action. Until corrective action is taken, accepted and acknowledged, the activation 800 and control 200, 500 modules will be interrupted.
When the driver moves the gear shift from “park” to “reverse” 802 and presses or turns a trailer backup steering input apparatus 125 a rear view camera image may appear in a display of the HMI. If at any time during the reversing process the hitch angle becomes too large for the system to control the curvature of the trailer, the TBA will provide a warning to the driver to pull forward to reduce the hitch angle. If at any time during the reversing process the system is unable to track the hitch angle target, the driver is presented with instructions to correct the problem. If at any time the vehicle speed exceeds that predetermined activation speed, the driver is visually and audibly warned to stop or slow down.
When all of the conditions of the activation module are met and maintained, the control module may begin. The control module executes the directives described above with reference to
Referring now to instructions processible by a data processing device, it will be understood from the disclosures made herein that methods, processes and/or operations adapted for carrying out trailer backup assist functionality as disclosed herein are tangibly embodied by non-transitory computer readable medium having instructions thereon that are configured for carrying out such functionality. The instructions are tangibly embodied for carrying out the method 200, 600, 700 and 800 disclosed and discussed above and can be further configured for limiting the potential for a jackknife condition such as, for example, by monitoring jackknife angle through use of the equations discussed in reference to
In a preferred embodiment of the disclosed subject matter, a trailer backup assist control module (e.g., the trailer backup assist control module 120 discussed above in reference to
Trailer Target Placement and Monitoring
The vehicle trailer backup assist system may utilize a target placed on the trailer to serve as the hitch angle detection component 155. In doing so, the trailer backup assist system may employ information acquired via image acquisition and processing of the target for use in the hitch angle detection apparatus 130, according to one embodiment. According to other embodiments, the target may be used to identify if a connected trailer has changed, trailer connection or disconnection, and other trailer related information. The target is an identifiable visual target that can be captured in an image by the video imaging camera and detected and processed via image processing. According to one embodiment, the target may include an adhesive target, also referred to as a sticker, that may be adhered via adhesive on one side onto the trailer, preferably within a target placement zone, such that the camera and image processing may detect the target and its location on the trailer to determine trailer related information, such as the hitch angle between the trailer and the towing vehicle. The trailer backup assist system may provide to the user one or more image(s) of the trailer target zone for proper placement of the target to assist with placement of the target on the trailer. Additionally, the vehicle trailer backup assist system may monitor the target to determine if the target has been correctly placed within a desired target placement zone and provide feedback alert(s) to the user. Further, the trailer backup assist system may monitor the trailer connection by monitoring the target to determine if the target has moved to determine whether the same trailer remains connected to the tow vehicle, and may initiate action in response thereto. Further, the trailer backup assist system may monitor the hitch angle or the target to determine if the trailer may have been changed out (i.e., disconnected and replaced with another trailer), and may initiate action in response thereto.
Referring to
A camera 20 is shown as an input for providing video images to the target monitor controller 10 of the vehicle trailer backup assist system 105. The camera 20 may be a rearview camera mounted on the tow vehicle in a position and orientation to acquire images of the trailer towed by the vehicle rearward of the vehicle. The camera 20 may include an imaging camera that generates one or more camera images of the trailer including the region where a target placement zone is expected to be located on the trailer. The camera 20 may include a video imaging camera that repeatedly captures successive images of the trailer for processing by the target monitor controller 10. The target monitor controller 10 processes the one or more images from the camera 20 with one or more image processing routine(s) 16 to identify the target and its location on the trailer. The target monitor controller 10 further processes the processed images in connection with one or more of routines 900, 920, 940, 960 and 990.
The trailer monitor controller 10 may communicate with one or more devices including vehicle exterior alerts 24 which may include vehicle brake lights and vehicle emergency flashers for providing a visual alert and a vehicle horn for providing an audible alert. Additionally, the trailer monitor controller may communicate with one or more vehicle human machine interfaces (HMIs) 25 including a vehicle display such as a center stack mounted navigation/entertainment display. Further, the trailer monitor controller 10 may communicate via wireless communication 22 with one or more handheld or portable devices 26, such as one or more smartphones. The portable device 26 may include a display 28 for displaying one or more images and other information to a user. The portable device 26 may display one or more images of the trailer and the target location within a desired target placement zone on display 28. In addition, the portable device 26 may provide feedback information about the vehicle target connection including visual and audible alerts.
Referring to
The vehicle 100 is equipped with a video imaging camera 20 shown located in an upper region of the vehicle tailgate at the rear of the vehicle 100. The video imaging camera 20 is elevated relative to the target placement zone(s) and has an imaging field of view and is located and oriented to capture one or more images of the trailer 110 including a region containing one or more desired target placement zone(s). It should be appreciated that one or more cameras may be located at other locations on the vehicle 100 to acquire images of the trailer 110 and the target placement zone(s) 32.
In order to utilize a target on a trailer that is not currently equipped with a suitable pre-existing target, a user 2 may be instructed or directed to place the target 30 onto the trailer 110 within a desired target placement zone 32 so that the camera 20 may capture one or more images of the target 30 to determine trailer related information for the trailer backup assist system, such as hitch angle information for the hitch angle detection apparatus 130. In doing so, a user 2 may be prompted by an audible or visual message on an HMI such as the vehicle HMI 25 or portable device 26 to place the target 30 on the trailer 110. The vehicle HMI 25 may include visual and/or audible outputs generating instructions for proper target placement.
To allow for efficient and proper placement of the target 30 onto the trailer 110, the trailer backup assist system employs a target placement assist method or routine 900 shown in
One example of a displayed image on the display 28 of a portable device 26 showing an overlay of the target location for the target to be placed on the trailer is illustrated in
Accordingly, the target placement assist method 900 advantageously assists the user with placement of the target 30 onto the trailer 110 in a manner that is simple to use, accurate and efficient. The user 2 may easily transport a portable device having a display to communicate with the vehicle and view the correct placement location for the target prior to and during the target placement procedure without having to return to the vehicle or otherwise be prompted for target placement.
The trailer backup assist system 105 further includes a target monitoring method or routine for monitoring placement of the target on the trailer and providing feedback to the user as to whether the target has been placed within a proper target placement zone. A user may place a target on the trailer in various ways. In some situations, the user may be prompted by the TBA system via a vehicle HMI to place a target on the trailer and may be given instructions as to the location. The user may employ the target placement assist method 900 to assist with placement of the target on the trailer. In other situations, the user may place the target on the trailer using their best judgment or following instructions printed on the target or packaging provided therewith. In any event, once the target is placed on the trailer, the target monitoring method 920 will monitor the location of the target relative to the trailer and provide feedback to the user as to correct or incorrect placement of the target on the trailer.
The target monitoring method 920 is illustrated in
At step 928, the system generates one or more images of the target placement zone on the towed trailer. The system then processes the one or more images to determine the presence of a target within a desired target placement zone at step 930. The desired target placement zone may be determined by criteria, such as distance from the trailer hitch connection formed by the coupler assembly 114, distance from a centerline of the longitudinal axis of the trailer, height of the camera relative to the trailer, and distance of the camera from the trailer. At decision step 932, method 900 determines if the target has been detected by the processed image(s) and, if not, returns to step 926 to prompt the user via an HMI to place the target on the trailer.
If the target has been detected by the processed images, the vehicle trailer backup assist system provides a feedback alert to the user at step 934. The feedback alert may include one or more of vehicle exterior alerts including visual alerts, such as flashing the vehicle brake lights and/or flashing the vehicle emergency flashers, and/or audible alerts, such as sounding the vehicle horn. Additionally, the feedback alerts may include providing a message via the portable device 26, providing an audible tone via the portable device 26 or a visual lighted indication via the portable device 26. Further, feedback alerts may include sending a text message or audible instructions to a user via a portable device, such as a phone or computer. It should be appreciated that other vehicle exterior and alternative feedback alerts may be communicated to the user to indicate that proper placement of the target has been detected on the trailer. Alternatively, the feedback alerts could be used to indicate improper placement of the target on the trailer. Once the trailer is properly equipped with the target in the proper location, the trailer backup assist system may process information by monitoring the target to determine the hitch angle and other trailer towing related functionality.
The target 30 may include a sticker having adhesive on the bottom surface and a predetermined image pattern of a certain size and shape provided on the top surface for capture by the video camera and recognition by the image processing. The target 30 may have a rectangular shape, according to one embodiment, and may have a camera image recognizable pattern such as the checker pattern shown. The image processing may include known image pattern recognition routines for identifying a target pattern and its location on a trailer. However, it should be appreciated that other target shapes, sizes and patterns may be employed. It should further be appreciated that the target may otherwise be connected to the trailer using connectors, such as fasteners, which may connect to the trailer or to an attachment to the trailer. It should further be appreciated that the target can be attached via magnet, glued on, painted on, or any number of other suitable means.
It should be appreciated that not all trailers are necessarily configured to provide a well-suited location for placement of a target sticker on the trailer. Accordingly, a target location may be added to a given trailer by use of a target mounting system 40 as shown in
The target moved detection method includes an initial setup routine 940 and subsequent processing routine 960 for target moved detection used for prompting the entry of trailer information. The target moved detection method determines if the location of a hitch angle target on a trailer, such as a trailer tongue, has moved and may also determine if the distance has changed. Images of the target in a previously stored image and a newly acquired image are compared to determine if the location and/or distance to the target has changed. The comparison may include comparing camera image pixel sizes of the images. If either the location or the distance changes, the user is then prompted by an HMI to reenter new trailer information for subsequent processing of the trailer backup assist system.
The initial setup routine 940 is illustrated in
Referring to
Examples of images of the trailer and the target moved to a different position are illustrated in
Target monitor controller 10 further processes a trailer connection monitoring routine 990 to determine whether a trailer is connected to the vehicle and whether a new trailer may have been connected. When the trailer is disconnected from the vehicle, the target information and the hitch angle information may be unavailable for a period of time. Accordingly, the trailer connection monitoring method 990 monitors the availability of the hitch angle data and/or the detection of the target to determine if the hitch angle data or target data is lost for a substantial period of time. If this occurs, the driver is then prompted via an HMI to reselect the attached trailer or to re-enter trailer configuration data to ensure that the wrong trailer information is not employed.
The trailer connection monitoring routine 990 is illustrated in
Depending on the type of hitch angle system, the hitch angle signal may drop or become unavailable for different reason, but one potential reason is that the trailer has been disconnected from the vehicle. A disconnected trailer may also result in the target detection being unavailable. As such, a check is made to see how much time has expired since the hitch angle signal or target detected has been dropped. If the hitch angle or target detection has been dropped for a time period of less than X seconds, then routine 990 returns to track the hitch angle or target at step 996. If the hitch angle or target detection has been dropped for a time period greater than X seconds, then the user is prompted via an HMI to reselect or re-setup the trailer configuration in step 1000. The time period X is set to represent a reasonable amount of time needed to swap or change-out trailers. For example, for extremely small, lightweight trailers, it may be possible to swap trailers out in less than sixty (60) seconds, so this could be a reasonable time period. According to one embodiment, the time period X is set for thirty (30) seconds.
While the hitch angle is monitored to determine disconnection of a trailer from the vehicle, it should be appreciated that the trailer connection monitoring routine 990 may monitor detection of the target as an alternative, such that if the target is no longer detected for X seconds, then the vehicle driver may be prompted to reselect or reconfigure the trailer.
Secondary Hitch Angle Sensor System
For the trailer backup assist system 105, as previously described, it is advantageous to use information that is representative of an angle between the vehicle and a trailer attached to the vehicle, also known as the hitch angle γ or trailer angle. In addition to the trailer backup assist system 105, it is contemplated that other vehicle systems may utilize hitch angle information as an input to the system, whereby the hitch angle information may be manipulated by a controller or microprocessor associated with the vehicle 100. In some embodiments, a measured hitch angle γ(m) may not provide an accurate measurement of the actual hitch angle γ(a) to a requesting system, which may introduce a potential for inadequate or improper vehicle system control, especially in situations where the hitch angle information may be important to the vehicle system being controlled, such as the trailer backup assist system 105. Furthermore, as previous mentioned, the hitch angle signal may drop-out or become unavailable for different reasons, such as the hitch angle detection apparatus 130 momentarily being unable to sense the relative position of trailer 110, or more specifically, the camera 20 being unable to track the hitch angle target 30 or other hitch sensors, such as a potentiometer, magnetic, optical, or mechanical based sensors, being unable to provide a constant hitch angle measurement, which may similarly cause errors or other disruption in operating the trailer backup assist system 105. Accordingly, an accurate and consistent estimate of the actual hitch angle γ(a) is desired, including for a means to confirm the accuracy of a measured hitch angle γ(m).
Referring to
In the embodiment illustrated in
As also shown in
With further reference to
The blind spot system 1216, according to one embodiment shown in
The cross traffic alert system 1218, as shown in
Referring to
The trailer monitoring controller 1230 illustrated in
As also illustrated in
The method for estimating the actual hitch angle γ(a) using the sensor system 1200 of the trailer backup assist system 105 is illustrated in
Still referring to
While the illustrated embodiment of the sensor system 1200 includes a primary sensor 1202 and a secondary sensor 1204, it should be appreciated that the sensor system 1200 may include addition sensors (tertiary sensor, quaternary sensor, etc.) with additional corresponding indicators for confirming the accuracy of the indicator 1206 from the secondary sensor 1204 and the measured angle γ(m) from the primary sensor 1202. It is also be understood that the sensor system 1200 may additionally, or alternatively, be adapted for use with other vehicle related applications, such as trailer sway limiters or other conceivable applications relying upon the accuracy of the measured hitch angle γ(m).
Hitch Angle Estimation and Verification
According to an additional embodiment for estimating the actual hitch angle, a system uses an estimated distance between a wireless receiver on the vehicle and a wireless transmitter on the trailer. The wireless receiver on the vehicle is located at a predetermined distance from a trailer mount and the wireless transmitter on the trailer is located at an end of the trailer opposite the trailer mount. With respect to this embodiment, the system includes a controller for monitoring power returns of a signal transmitted from the transmitter to the receiver and for estimating the distance between the transmitter and the receiver as a function of a path loss propagation of the transmitted signal. The actual hitch angle is then estimated using the estimated distance, the predetermined distance, and a trailer length.
Referring now to
As shown in
A wireless transmitter 1280 is positioned on the trailer 110 at a known location, preferably at the end of the trailer. This wireless transmitter 1280 is in communication with the wireless receiver 1270 that is located on the vehicle 100. The wireless receiver 1270 has been placed at a known location of the vehicle 100 such that a reference distance, dr, from the receiver 1270 to the hitch ball 15 at the rear of the vehicle 100 is known and stored in memory 1274. Examples of wireless transmitting and receiving devices that may be used are Radio Frequency Identification (RFID), Bluetooth, and the like. As discussed above, the wireless receiver 1270 is positioned at a location on the vehicle 100 the predetermined distance, dr, from the vehicle's trailer mount or hitch ball 15. The wireless transmitter 1280 and the wireless receiver 1270 are compatible units that transmit and receive signals between the vehicle 100 and the trailer 110. The controller 1272 monitors the power returns of the transmitted signals. By monitoring the power returns of signals sent by the transmitter to the receiver, the controller 1272 may estimate a distance, d, between the vehicle 100 and the trailer 110.
The disclosed subject matter also uses a trailer length, lT. This value may be a known value entered by the driver, stored in controller memory, or otherwise sensed, calculated or estimated. For example, an accurate estimate of trailer length, lT, is possible using measurements of the signal transmitted from the wireless transmitter 1280 on the trailer 110 to the wireless receiver 1270 on the vehicle 100 when the hitch angle is zero. It is also possible to estimate the trailer length when the measurements are taken while the vehicle yaw rate is zero for a predetermined period of time.
The hitch angle is thereby estimated using the trailer length, lT, and path loss propagation of a signal transmitted from the transmitter on the trailer 110 to the receiver 1270 on the vehicle 100. The hitch angle estimate may then be used as an input for control algorithms associated with a variety of vehicle systems 1281 such as trailer sway, trailer backup assist, stability control and other systems. Alternatively, the hitch angle estimate may be used to verify, or validate, the measurement taken by a hitch angle sensor.
Referring to
A2=B2+C2−2BC cos(a)
The vehicle 100 has the trailer 110 attached thereto with the receiver 1270 located on the vehicle a predetermined reference distance, dr from the trailer hitch ball 15, which corresponds to B for the triangle reflecting the law of cosines in
Referring to
An operation 1284 is performed for requesting hitch angle estimation. A request for hitch angle estimation may come from a vehicle control system 1281 that requires the information as an input to the control algorithm associated therewith or it may come from a control system 1281 that wants to validate or verify a hitch angle provided by a hitch angle sensor. Examples of vehicle control systems 1281 that may request hitch angle information may be a trailer backup assist system 105, a trailer sway control system, a trailer brake control system, and a vehicle dynamic control system such as roll stability control or yaw stability control. These are only a few examples of systems 1281 that may utilize hitch angle information as an input to a control algorithm.
An operation 1286 is performed to monitor power returns of signals transmitted from the trailer 110 to the vehicle 100. Path loss is proportional to the square of the distance between the transmitter and the receiver and power returns of signals transmitted may be used to estimate a distance between the transmitter and the receiver. The power returns are measured, at the receiver, at predetermined time intervals and stored in controller memory over a predetermined period of time. The power returns may be accessed by the controller for various operations and/or functions that use the values to estimate hitch angle.
An operation 1288 is performed to estimate the distance, d, between the transmitter and the receiver. Estimating the distance, d, between the wireless transmitter and the wireless receiver 1270 is accomplished by using the, measured power returns or measured path loss of the signal being transmitted. Path loss is proportional to the square of the distance between the transmitter and the receiver, and also to the square of the frequency of the transmitted signal. Signal propagation may be represented by Friis transmission formula:
where,
Pt is the transmission power in Watts,
Gt and Gr are gains associated with the receiver and the transmitter respectively,
λ is the wavelength,
L are system losses, and
d is the distance between the transmitter and the receiver.
Accordingly, transmission power decreases at a rate proportional to d2. Therefore, knowing the path loss, PL, associated with the transmitted signal will provide an estimate of the distance, d, between the transmitter and the receiver. Path loss (PL) is represented by the following equations:
Pr decreases at a rate that is proportional to d2. The power of the signal received at the receiver may be represented as:
The distance, d, may be derived from this formula and represents the overall distance between the transmitter on the trailer and the receiver on the vehicle. The distance, d0, is a known received power reference point and the distance, df, is a far-field distance.
The reference distance, dr, is known. If the trailer length, lT is known, then an operation 1289, using the distance, d, the trailer length, lT, the known reference distance, dr, between the receiver and the trailer hitch, and the law of cosines, is performed to calculate the hitch angle. From the law of cosines, provided above, the hitch angle is given by:
An operation 1290 is performed in which the vehicle system that is requesting the information receives the hitch angle estimation. The disclosed subject matter provides an estimate of hitch angle even when a hitch angle sensor is unavailable. If a system relies on a hitch angle sensor, the disclosed subject matter may provide verification, as a redundant sensor, that the hitch angle sensor is operating properly.
As discussed above, the trailer length, lT, may be a known value stored in memory or it may be a value that is calculated according to the disclosed subject matter. The trailer length may be calculated 1292 by comparing distances, d, between the transmitter and the receiver that have been estimated and stored in memory over a period of time. A predetermined number of distance estimates may be stored in controller memory. A comparison of the stored distances may result in a largest distance may be identified. The largest distance estimate may be associated with a zero hitch angle. This identified largest distance, less the known reference distance, dr will be representative of, and may be stored as, the trailer length, lT.
As an alternative, the trailer length, lT, may be estimated using a yaw rate provided by a yaw rate sensor on the vehicle to determine when the trailer is a zero hitch angle. A yaw rate sensor is typically available as part of the sensor system 1200 on the vehicle. A zero yaw rate is an indicator that a vehicle is travelling along a straight path, i.e., the vehicle is not turning. The fact that the yaw rate is zero alone is not adequate to identify a zero hitch angle because the vehicle may have just stopped turning even though a non-zero hitch angle exists. However, monitoring yaw rate over time will provide confirmation that the vehicle has driven straight forward for a sufficient predetermined period of time while maintaining a zero or near zero yaw rate. A zero yaw rate, sensed over time, provides an indication that the trailer has straightened out and it can be inferred that the hitch angle is zero at that point. Upon verification of zero hitch angle, the operation to calculate trailer length 1292 is performed. The estimated distance between the transmitter and the receiver when the hitch angle is zero less the predetermined distance, dr, defines the trailer length, lT.
The predetermined period of time that the yaw rate should remain at zero before the assumption that the hitch angle is zero will be associated with an actual distance the vehicle trailer combination needs to travel to ensure that the hitch angle is zero. This may be determined through testing and stored in the controller memory.
The disclosed subject matter is advantageous in that it provides an estimate of hitch angle whether or not a hitch angle sensor is present on a vehicle. The disclosed subject matter is even advantageous for a vehicle that has a hitch angle sensor in that it provides a method for verifying, or validating, the accuracy of a hitch angle sensed by a hitch angle sensor. This is especially important for vehicle systems that rely critically on the value of the hitch angle being sensed, for example, trailer backup assist systems, trailer sway control systems and trailer brake control systems.
Hitch Angle Calibration
As previously mentioned with reference to
With reference to
As shown in
Referring to
As reflected in the diagram shown in
Furthermore, the yaw rate of the trailer can be represented with the following equation:
Where,
δ is the steering angle of the front wheels
D is the distance from the hitch to the trailer axle
W is the vehicle wheelbase (distance between both axles)
L is the distance from the vehicle rear axle and hitch
γ is the hitch angle
Accordingly, when the yaw rate of the vehicle 100 and the trailer 110 become equal, the actual hitch angle γ(a) will likely be constant, such that the desired hitch angle provided by the trail backup steering input apparatus 125, such as the previously described rotatable input control device shown in
c=α cos γ+b sin γ
This equation can be rewritten as follows:
c=a√{square root over (1−sin2γ)}+b sin γ
The above equation can be solved with the quadratic equation that solves for the hitch angle γ. Thereafter, when breaking up the hitch angle γ into a measured hitch angle γ(m) and an offset angle γ(o), the equation can be rewritten as follows:
Accordingly, the hitch angle offset γ(o) may be determined as a function of the length D of the trailer 110, the wheelbase length W of the vehicle 100, and the distance L from a rear axle of the vehicle 100 to the trailer 110 as shown in
As illustrated in
At step 1324, the system conducts the initiating routine 1310 to further confirm that the vehicle 100 and trailer 110 combination is in a condition to determine the offset γ(o) between the measured hitch angle γ(m) and the actual hitch angle γ(a). As shown in
With further reference to
In an additional embodiment of the hitch angle calibration routine 1308, as illustrated in
In the previously described embodiment of the hitch angle calibration routine 1308 with reference to
With reference to
Still referring to
Once the sensor readings are being received and the vehicle is being steered straight and driving forward, the illustrated embodiment of the hitch angle calibration routine 1308 then proceeds to process an initiating routine 1310 at step 1358. The initiating routine 1310 of the present embodiment may, similar to the initiating routine illustrated in
As also illustrated in
Referring now to
Alternatively, if the vehicle 100 is reversing or instructed to reverse, at step 1384, once the vehicle 100 is reversing, the system proceeds to sense the steering angle δ of the vehicle 100 at step 1386 and sense the hitch angle γ(m) at step 1388 to then determine the hitch angle rate and the steering angle rate at step 1390. At step 1392 the system determines when both the hitch angle rate and the steering angle rate are substantially zero. When both these values are substantially zero, the hitch angle calibration routine 1308 may determine the offset γ(o) of the measured hitch angle γ(m) based upon the length D of the trailer 110, the wheelbase length W of the vehicle 100, and the distance L from the rear axle of the vehicle 100 to the trailer 110, as generally set forth in the embodiment of the hitch angle calibration routine 1308 described with reference to
Hitch Angle Sensor Assembly
As disclosed herein, it is advantageous to use information that is representative of a hitch angle between a vehicle and a trailer attached to the vehicle, also described herein as the actual hitch angle γ(a) or trailer angle. For instance, the trailer backup assist system 105 and other conceivable vehicle systems may utilize hitch angle information as an input into the system. In accordance with the previous disclosure, the estimated hitch angle γ may be derived from information collected from one or more sensors on the vehicle, one or more sensors on the trailer, a hitch angle detection apparatus 130 on the vehicle 100, a hitch angle detection component 155 on the trailer 110, or other conceivable sensor systems.
Referring now to
As shown in the embodiment illustrated in
As also shown in
With further reference to the embodiment illustrated in
Referring now to the embodiment illustrated in
As illustrated in
With further reference to
Still referring to
As shown in the embodiment illustrated in
Accordingly, as further illustrated in the embodiment shown in
With reference to
Additionally, in
Horizontal Camera to Target Distance Calculation
In order to implement some of the features described herein, a user is typically required to set up the trailer backup assist system 105. This can include properly placing a target on a trailer as well as obtaining one or more measurements associated with a particular vehicle-trailer configuration. Two user-obtained measurements can include a horizontal camera to target distance and a target to ground distance. Since the user is typically charged with performing these measurements, there is a possibility for erroneous measurements being reported to the trailer backup assist system 105, thereby potentially diminishing the accuracy of hitch angle detection and/or other actions performed by the trailer backup assist system 105. To lessen the likelihood of a user reporting erroneous measurements during the set up process, a system and method is disclosed herein that at most, requires the user to measure only the target to ground distance, which is supplied to the trailer backup assist system 105 and used to calculate the horizontal camera to target distance. In this manner, the potential for human error is reduced and as an additional benefit, the process of setting up the trailer backup assist system 105 is shortened.
Referring to
The controller 2010 can be any controller of an electronic control system that provides for setup functionality of the trailer backup assist system 105. The controller 2010 can include a processor 2030 and/or other analog and/or digital circuitry for processing one or more routines. Additionally, the controller 2010 can include memory 2035 for storing one or more routines. According to one embodiment, the controller 2010 can be configured to receive and process information from the input device 2005 and image data from the camera 2000.
Discussion now turns to a method for calculating a horizontal camera to target distance using the trailer backup system 105. The method will be described below as being implemented by the controller 2010. As such, this method may be a routine executed by any processor (e.g., processor 2030), and thus this method may be embodied in a non-transitory computer readable medium having stored thereon software instructions that, when executed by a processor, cause the processor to carry out its intended functionality.
With reference to
With respect to the illustrated embodiment, the camera is exemplarily shown coupled to a rear member 2038 (i.e. tailgate) of the vehicle 2015 and the target 2020 is positioned longitudinally across a tongue portion 2040 of the trailer 2025. In the illustrated embodiment, the camera 2000 has a vertical field of view defined by an upper field extent 2045 and a lower field extent 2050 for imaging a rear vehicle area that includes the target 2020. To determine the horizontal camera to target distance dh using the method described herein, the controller 2010 calculates a first horizontal distance d1 and a second horizontal distance d2 that are summed together to yield the horizontal camera to target distance dh.
The first horizontal distance d1 corresponds to a horizontal distance from the camera 2000 to an intersection point pi between the lower field extent of the vertical field of view and a centerline longitudinal axis X of the target 2020, and is expressed by equation 1:
d1=d2 tan θ
where,
dh: horizontal camera to target distance;
d1: first horizontal distance;
d2: second horizontal distance;
dv: vertical camera to target distance;
θ: a known angle between a vertical extent Y of the rear member 2038 of the vehicle 2015 and the lower field extent 2050 of the vertical field of view of camera 2000;
tg: target to ground distance;
rh: known receiver height;
dm: draw bar drop measurement;
pi: intersection point;
pm: target midpoint.
To calculate the vertical camera to target distance dv, it is preferable for the user to measure a target to ground distance tg, which can be supplied to the controller 2010 via the input device 2005. Alternatively, in some cases, the controller 2010 can estimate the target to ground distance tg within an acceptable tolerance by using a known receiver height rh for the target to ground distance tg value in instances where a straight draw bar 2055 is used. In instances where the drawbar 2055 has a drop, the controller 2010 can be supplied with a draw bar drop measurement dm, which is typically known to the user, and estimates the target to ground distance tg by subtracting the draw bar drop measurement dm from the receiver height rh (see
Once the first horizontal distance d1 has been calculated, the controller 2010 next calculates the second horizontal distance d2, which corresponds to a distance from the intersection point pi to a target midpoint pm, and is expressed by equation 2:
dv=√{square root over (da2+db2−2dadb cos γ)}
where,
da: camera to intersection point distance;
db: camera to target midpoint distance;
γ: angle between the camera to target midpoint distance db and the camera to intersection point distance da.
Having previously calculated the vertical camera to target distance dv and the first horizontal distance d1, the camera to intersection point distance da can be calculated using the Pythagorean Theorem.
Angle γ may be calculated by observing a relationship between the vertical field of view and a corresponding camera image. This relationship is shown by equation 3:
where,
δ: vertical field of view angle;
pc: pixel count taken from the lower field extent to the target midpoint pm with respect to camera image 2060, as shown in
vr: vertical resolution of the camera image 2060.
Pixel count pc can be determined using any suitable image recognition method and naturally varies based on the positioning of the target 2020. The vertical field of view angle δ and the vertical resolution vr are each typically known from the camera 2000 specification and the corresponding values can be stored to memory (e.g., memory 2035) and supplied to the controller 2010 in any suitable manner. Once the controller 2010 receives the pixel count pc, vertical field of view angle δ, and vertical resolution vr, equation 3 can be solved to calculate angle γ.
Camera to target midpoint distance db can be calculated using equation 4:
where,
dv: vertical camera to target distance;
α: angle between the camera to target midpoint distance db and the centerline longitudinal axis X of the target.
By recognizing that the vertical camera to target distance dv is perpendicular with the centerline longitudinal axis X, angle α can be calculated by subtracting 90 degrees, angle δ, and angle γ from 180 degrees. Having done this, the camera to target midpoint distance db can be calculated using equation 4, which allows for the second horizontal distance d2 to be calculated using equation 2. Finally, the horizontal camera to target distance dh can be calculated by summing together the first horizontal distance d1 and the second horizontal distance d2.
Trailer Length Estimation in Hitch Angle Applications
Many of the embodiments of the trailer backup assist systems described herein may utilize parameters such as trailer a length. As discussed herein, a memory (e.g. the memory 1274) may be configured to store various parameters related to the vehicle 100 and a trailer. For example, parameters may include known, fixed vehicle measurements such as wheel base, vehicle length, trailer length and distances from known parts of the vehicle. Though the wheel base and vehicle length may remain fixed throughout the life of the vehicle, a trailer length may change depending on a particular trailer that is in connection with the vehicle. In some implementations, the trailer length may be provided by the customer during a setup process as an input to a system. However, manually entering the trailer length may lead to an accidental input of an imprecise length. Depending on the magnitude of error of a manually entered length, controller performance may be negatively affected.
The systems and methods described herein provide various methods to estimate a trailer length. The various embodiments may provide for systems that are operable to dynamically identify a trailer length while the vehicle 100 is travelling in either the forward or reverse direction. In some implementations, the trailer length may be monitored and updated periodically during operation of the vehicle 100. The trailer length may also be set initially during setup routine following the attachment of a trailer to the vehicle 100. As described herein in detail, the systems and methods introduced in this disclosure provide for improved convenience and operation of the trailer backup assist system 105.
Referring to
δ: steering angle at front wheels 2106 of the vehicle 2102;
γ: hitch angle between the vehicle 2102 and the trailer 2104;
W: wheel base of the vehicle 2102;
L: length between a hitch point 2108 and a rear axle center-line 2110 of the vehicle 2102; and
D: length between hitch point 2108 and a trailer axle center-line 2112, wherein the position of the trailer axle center-line 2112 may be an effective, or equivalent, axle length for a trailer having a multiple axle configuration.
The kinematic model 2100 of
{dot over (γ)}=−(VR/W+VRL/(WD)cos(γ))tan(δ)−VR sin(γ)/D
For a particular vehicle, certain kinematic model parameters (e.g. W and L) may be constant. In some cases, these parameters may be preprogrammed into a memory, for example, the memory 1274. Other parameters may be measured by one or more sensors in communication with the control module 120. The velocity VR may be determined from the brake system control module 145 and communicated to the trailer backup assist control module 120. Such vehicle speed information can be determined from individual wheel speeds as monitored by the brake system control module 145 or may be provided by an engine control module.
The power steering assist control module 135 may provide the trailer backup assist control module 120 with information relating to the steering angle δ and/or a rotational position (e.g., turning angle(s)) of steered wheels of the vehicle 100. In certain embodiments, the trailer backup assist control module 120 can be an integrated component of the power steering assist system 115. For example, the power steering assist control module 135 can include a trailer backup assist algorithm for generating vehicle steering information as a function of all or a portion of information received from the trailer backup steering input apparatus 125, the hitch angle detection apparatus 130, the power steering assist control module 135, the brake system control module 145, and the powertrain control module 150.
The hitch angle γ may be communicated to the backup assist control module 120 by the hitch angle detection apparatus 130. The hitch angle γ may communicate an angle between a vehicle longitudinal axis 2114 and a trailer longitudinal axis 2116. The hitch angle detection apparatus 130 may work in conjunction with a hitch angle detection component and may detect the hitch angle by a variety of methods. In some implementations, the hitch angle γ is determined based on a camera-based apparatus such as, for example, a rear view camera of the vehicle 100. The hitch angle γ may also be measured via a number of sensors on or around the vehicle 100. Sensors may include various types of hitch angle sensors, such as resistive, inductive, ultrasonic, and/or capacitive type sensors, in addition to other hitch angle sensor systems discussed herein. From various permutations including various model parameters of the kinematic model 2100 that may be preprogrammed or monitored throughout operation of the vehicle 100, various systems and methods operable to accurately estimate the trailer length D are disclosed herein.
From the equation for gamma dot {dot over (γ)} with respect to time, a minimum error equation for the trailer length D can be derived to minimize the mean squared or root mean squared (RMS) error between an estimate of gamma {circumflex over (γ)}i+1 and a measured value of gamma γi+1 from the hitch angle sensor. As the samples i are collected, the accuracy of the trailer length increases as the {circumflex over (γ)}i+1 and γi+1 converge. Starting with the gamma dot equation, s, is designated to be the distance traveled by the vehicle 100. Then by sampling at Δt intervals with Euler's approximation, a resulting equation is determined to be:
{circumflex over (γ)}i+1=Δs[1/W+L/(WD)cos(γi)tan(δF i)+sin(γi)/D].
Therefore:
{circumflex over (γ)}i+1=γi+g1(i)−g2(i)/D,
wherein:
g1(i)=Δs tan(δi)/W;
and
g2(i)=−Δs[L cos(γi)tan(δi)/W+sin(γi)].
In order to minimize the mean squared error between {circumflex over (γ)}i+1 and γi+1, the conditions where the mean squared error is minimized between {circumflex over (γ)}i+1 and γi+1 are then determined. Based on the determined conditions, the equation is then simplified and arranged to provide a minimum error equation for the trailer length D as follows:
The minimum error equation may be applied to determine the trailer length D when the vehicle 100 is traveling in either the forward or reverse direction. Due to the nature of the mean squared error calculation, the method may impose conditions including variations in the wheel steer angle δ for the estimated trailer length to converge toward an actual trailer length. The minimum error equation also requires that the vehicle 100 be in motion to calculate the trailer length D.
A flow chart for a method 2130 for utilizing the minimum error to determine the trailer length D is shown in
The velocity VR of the vehicle 2102 may be received from the engine control module, the wheel steer angle or steering angle δ may be received from the power steering assist control module 135, and the trailer hitch angle γ may be received from the hitch angle detection apparatus 130. Though the data inputs are described as being received from the specific hardware devices (e.g. the power steering assist module 135), the data inputs may be received from any devices implemented by the trailer backup assist control module 120 to monitor the kinematic properties of the vehicle 2102 discussed herein. Each of the data inputs may be sampled by the microprocessor 1304 or a similar processor at predetermined time intervals. For example, each of the data inputs may be sampled multiple times per second to update the measured values of VRi, γi, and δi. In an exemplary implementation, the data inputs may be updated at a sampling rate ranging from 1 Hz to 1000 Hz.
With the wheel steer angle or steering angle δ and the trailer hitch angle γ, g1(i) and g2(i) are calculated by the at least one processor (2136). The method 2130 may then continue to determine if VRi, |γ|, and |δ| are each in a predetermined range for the trailer length to be accurately calculated based on the conditions of calculation for the minimum error calculation method (2138). For example, the velocity VRi of the vehicle 100 may be required to be less than ±15 Kph and not equal to zero. This may ensure that the vehicle 100 is in motion when the trailer length is calculated and also ensure that an error associated with the measurements of γi and δi is minimized. Additionally, the values of |γi|, and |δi| are compare to predetermined values to ensure that the change in each of the angles is sufficient to ensure that the mean squared difference of the respective values converge. For example, the microprocessor 1304 may determine |γ| is greater than a first predefined value and |δ| is greater than a second predefined value. In one exemplary implementation, the microprocessor 1304 may require that |γ|>0.035 radians, and |δ|>0.017 radians. If the microprocessor 1304 determines that any of the input parameters VRi, |γ|, and |δ| are outside the conditions of step 2138, the method 2130 may start over by incrementing i, to continue to attempt to calculate the trailer length D (2140).
If the microprocessor 1304 determines that VRi, |γ|, and |δ| are within the conditions of step 2138, the trailer length is calculated using the minimum error equation as Di,min_err (2142). Following the calculation of Di,min_err, the microprocessor 1304 continues to compare value of Di,min_err to a range of expected trailer lengths (2144). For example, a minimum trailer length may range from a minimum of approximately 1 m to a maximum of approximately 12 m. In an exemplary implementation, a minimum trailer length may be approximately 1.8 m and a maximum trailer length may be 10 m. If Di,min_err is outside the minimum and maximum values expected for a trailer length, the trailer length D may be set to 1.8 m (e.g. a minimum trailer length)(2146). If Di,min_err is within the minimum and maximum values expected for a trailer length, the trailer length D is set to Di,min_err (2148).
Steps 2136-2146 demonstrate a method for calculating Di,min_err and include a various controls and conditions to ensure that the trailer length D may be calculated accurately based on the minimum error approach and without computation errors (e.g. dividing by zero, etc.). Steps 2136-2146 are referred to hereinafter as the minimum error approach and referenced as step 2150 for clarity. The minimum error approach 2150 may be combined with a variety of other approaches to ensure that noise that may be received in conjunction with the steering angle δ and the trailer hitch angle γ is minimized to allow the trailer length D to be accurately estimated. The minimum error approach 2150 may be used independently and in combination with a variety of methods for calculating the trailer length D to help ensure that an error in the estimations of the trailer length D is minimized.
Referring now to
C: center of rotation of the vehicle 2102;
r: curvature radius between the vehicle 2102 and the trailer;
T: track width of the vehicle 2102;
x: axial distance from the intersection of the trailer center-line 2116 to the rear axle center-line 2110; and
y: lateral distance from the intersection of the trailer center-line 2116 to the rear axle center-line 2110.
The kinematic model 2160 relates the radius of curvature of the vehicle 2102 and the trailer 2104 dimensions together with the steering angle δ and the hitch angle γ. As shown in the following equation, the kinematic model 2160 of the vehicle 2102 and the trailer 2104 can be expressed in terms of the kinematic model parameters of the vehicle 2102 based on the Pythagorean Theorem.
(D+x)2+z(r+T/2+y)2
With the law of Sines, the trailer hitch angle γ is introduced into the equation.
The equation is further manipulated via substitution for x and y, as well as limited to conditions where the rotation of the vehicle 2102 and the trailer 2104 are stable. The rotation of the trailer 2104 is considered to stable when the trailer axle center-line 2112 is aligned with the center of rotation C of the vehicle 2102. A stable condition will normally exist when the trailer 2104 experiences limited slipping and/or bouncing that may change the alignment of the trailer 2102 with the track T of the vehicle 2102. A stable condition may be determined based on a change in the hitch angle γi between samples being smaller than a predefined value to determine if the trailer aligned with the vehicle. For example, if the |γi−γi+1| is less than 0.035 radians at a sampling rate of 20 Hz a stable condition may be assumed. The predefined value corresponding to |γi−γi+1| may vary based on the sampling rate of the hitch angle γi. Based on these considerations, an equation for the trailer length D is determined based on the curvature radius r between the vehicle 2102 and the trailer.
Finally, under conditions that the cos(γi)≠0, the equation is further simplified to provide the equation for the trailer length D based on the radius of curvature.
Drad=sin(γ)[W cot(δ)+T/2]−L cos(γ)
Di,rad may be calculated by the microprocessor 1304 based on data samples received from the power steering assist control module 135 and the hitch angle detection apparatus 130. Di,rad may be calculated based on the considerations that the cos(γ)≠0 and that the corresponding values of γ≠π/2 radians The cos(γ)≠0 when the trailer 2104 is in a jackknife condition such that the trailer 2104 is turned π/2 radians relative to the vehicle 2102. The conditions required to ensure that the calculation of the trailer length D based on the radius of curvature is accurately processed may similarly be ensured by utilizing the minimum error approach as discussed in reference to
Referring to
With the wheel steer angle δi and the trailer hitch angle γi, Di,min_err is calculated based on the minimum error approach 2150 by the processor (2176). As discussed previously, the minimum error approach may include determining if VRi, |γ|, and |δ| are each in a predetermined range. The determination may provide for the trailer length to be accurately calculated based on the operating conditions of the minimum error calculation method. These conditions are also sufficient to ensure that the trailer is in a stable towing condition. Additionally, the processor may verify that γi≠π/2 radians to determine if Di,rad may be calculated without error (2178). If γi=π/2 radians, the processor may report a jackknife condition to the operator of the vehicle 2102 (2180). The condition may be reported to the operator by the processor via the HMI device 102 or any form of audible or visual warning, for example illuminating an icon in a gauge cluster of the vehicle 2102.
If the processor determines that γi≠π/2, the method 2170 continues by calculating Di,rad based on the radius of curvature approach (2182). With the two separate estimates of the trailer length D, Di,min_err and Di,rad are compared to ensure that the trailer length D is accurately estimated (2184). The estimates are compared to determine if the absolute value of difference between Di,min_err and Di,rad is less than a first predetermined threshold or value, and if Di,rad is greater than or equal to a minimum trailer length. The minimum trailer length may be a second predetermined threshold or value. The difference between Di,min_err and Di,rad may vary based on the required accuracy of the trailer length D. In an exemplary implementation, the difference may be approximately 0.1 m. The minimum trailer length may vary based on an expected minimum length, and in an exemplary implementation may be approximately 1.8 m.
If Di,min_err and Di,rad do not meet the conditions of step 2184, the method 2170 may continue by incrementing i, to continue to attempt to calculate the trailer length D (2186). If the conditions are met in step 2184, the trailer length D is set to the estimate Di,rad (2188). Steps 2178-2182 demonstrate a functional implementation for calculating Di,rad and include various controls and conditions to ensure that the trailer length D may be calculated without computation errors (e.g. dividing by zero, etc.).
Steps 2178-2182 are referred to hereinafter as the radius of curvature approach and referenced as step 2190 for clarity. The radius of curvature approach 2190 is illustrated in the method 2170 in combination with the minimum error approach 2150, but in some implementations may be implemented independently as discussed herein. The radius of curvature approach 2190 provides various benefits when calculating the trailer length D. The radius of curvature approach 2190 converges immediately once the operating conditions are met and the calculations are simple. The simplicity of the calculations provides for limited processing requirements for the processor and may provide for decreased cost when compared to some alternative methods of calculating the trailer length D.
Referring now to
With the trailer length D estimated based on both the minimum error approach 2150 and the radius of curvature approach 2190, the processor may then compare Di,mine_err and Di,rad to ensure that the trailer length D is accurately estimated (2210). The estimates are compared to determine if the absolute value of difference between Di,min_err and Di,rad is less than a predetermined value, and if Di,rad is greater than or equal to a minimum trailer length. Similar to the method 2170, the difference between Di,min_err and Di,rad may vary based on the required accuracy of the trailer length D, and may be approximately 0.1 m. The minimum trailer length may be approximately 1.8 m. If Di,min_err and Di,rad do not meet the conditions of step 2210, the method 2200 may continue by incrementing i, to continue to attempt to calculate the trailer length D (2212). If the conditions are met in step 2210, the trailer length D is set to the estimate Di,min_err (2214).
The methods 2170 and 2200 demonstrate methods of estimating the trailer length D based on at least two different analytical methods to ensure that the trailer length D is accurately estimated. Each of the methods includes determining a first length estimate having a first uncertainty and a second length estimate having a second uncertainty. Based on a comparison of the values calculated for the first length and the second length, the calculated lengths are compared to validate an estimated value for the trailer length D. For example, the estimated trailer lengths Di,min_err and Di,rad may have a first uncertainty and a second uncertainty that is based at least in part on one or more assumptions applied when formulating the respective equations for Di,min_err and Di,rad. By comparing each of the estimated trailer lengths, the methods 2170 and 2200 validate the accuracy of a trailer length (e.g. Di,min_err or Di,rad) that is utilized to set the trailer length D. The comparison of the estimated lengths allows for the trailer length D to be calculated by only measuring the kinematic properties of the velocity VR, the wheel steer angle δ, and the trailer hitch angle γ. The methods 2170 and 2200 provide accurate and efficient implementations to determine the trailer length D without adding expensive monitoring hardware or other systems to the trailer backup assist control module 120.
Referring back to
At the hitch point 2108, the sine of the trailer hitch angle γ is expressed as follows.
Based on stable conditions for the rotation of the vehicle 2102 and the trailer 2104 and when the cos(γ)≠0, the ratio of the
referred to herein as the sine ratio, is represented as follows.
The equation may further be simplified by assigning a function m(W,T,L,γ,δ).
By substituting m(W,T,L,γ,δ), the sine ratio
is simplified as follows.
Finally, the sine ratio
is rearranged to solve for the trailer length D as the linear ratio Dsin ratio.
Based on the linear relationship of Dsin ratio, the equation is further simplified by the function S(W,T,δ) to provide the equation for the sine ratio method of estimating the trailer length D, where
From similar trigonometric relationships under the same conditions, the ratio of
referred to herein as the tangent ratio, is denoted as the following linear ratio.
From the equations for Dsin ratio and Dtan ratio, the general equation for a ratio method of estimating the trailer length D is represented for a given sample i as follows.
The trailer length may be calculated based on Di,ratio based on similar operating requirements or conditions as described in relation to the radius of curvature approach. For example, an initial condition for calculating Di,ratio may require that |γi−γi+1| is less than 0.035 radians at a sampling rate of 20 Hz. The predefined value corresponding to |γi−γi+1| may vary based on the sampling rate of the hitch angle γi and ensure that the trailer is in a stable towing condition.
Referring now to
With the trailer length D estimated based on both the minimum error approach 2150 and the radius of curvature approach 2190, the processor may then compare Di,min_err and Di,rad to ensure that the trailer length D is accurately estimated (2230). The estimates are compared to determine if the absolute value of difference between Di,min_err and Di,rad is less than a predetermined value, and if Di,rad is greater than or equal to a minimum trailer length. Similar to the methods 2170 and 2200, the difference between Di,min_err and Di,rad may vary based on the required accuracy of the trailer length D, and may be approximately 0.1 m. The minimum trailer length may be approximately 1.8 m. If Di,min_err and Di,rad do not meet the conditions of step 2230, the method 2220 may continue by incrementing i, to continue to attempt to calculate the trailer length D (2232). If the conditions are met in step 2230, the trailer length is calculated based on a running average of the sine ratio or the tangent ratio as Di,ratio (2234). The trailer length D is then set to the estimate Di,ratio (2236)
Additionally or alternatively, the method 2220 can use other operations in step 2234 to estimate the trailer length D. In one embodiment, the processor can match the averaged sine ratio or tangent ratio to a ratio value in a look up table. For purposes of illustration, a look up table 2400 is shown in
In addition or as an alternative to the abovementioned operations, step 2234 can include fitting the averaged sine ratio or tangent ratio to a predictive model 2402, such as that shown in
Accordingly, estimating the trailer length based on the sine or tangent ratios provides various benefits. For example, due to the linear nature of the function S(W,T,δ), the slope of Di,ratio is the product of the relationship among the kinematic properties of the wheel base W and the track width T of the vehicle 2102, as well as the measured value of the wheel steer angle δi. Also the y-intercept of Di,ratio is a function of the length L and the hitch angle γi. The simple characteristics of Di,ratio provide for an efficient method of estimating the trailer length D with limited processing requirements.
Referring to
(VΔt)2=Y2+X2−2YX cos(δ1−δ0)
Substituting
the relationship is represented by the following equation.
This is equation is then rearranged to solve for Y. Further, by applying a Taylor series for small changes in δδ=δ1−δ0, an equation is approximated for Y.
The above equation assumes that the change in Δδ is less than 0.03 radians for Δt of 0.05 seconds at a sampling rate of 20 Hz. From this assumption and by forcing the condition that (VΔt)sin(δn)>>WΔδ, the equation for the swept area Av of the vehicle 100 is described by the following equation.
Assuming the trailer 120 is located similar to the trailer 2104 relative to the vehicle 2102 as shown in
Finally for the cases where Δδ and Δγ are less than predetermined values, the equation for the trailer length D may be estimated as Di,SA.
The predetermined values of Δδ and Δγ may vary based on the particular implementation of a calculation method utilized by the vehicle 100. In some embodiments, Δδ and Δγ may be sufficiently small if each measurement is less than 0.035 radians at a sampling rate of 20 Hz. Under these conditions, Δδ and Δγ may have sufficiently small changes over time to ensure that the trailer 120 is in a stable condition, experiencing limited slipping and/or bouncing relative to the vehicle 2102. The swept area method described by the equation for Di,SA provides another accurate and useful method for estimating the trailer length D.
Referring now to
If the conditions are met in step 2266, the trailer length D is calculated based on the swept area method as Di,SA (2270). The trailer length D is then set to the estimate Di,SA (2272). If Δδ and Δγ do not meet the conditions of step 2266, the method 2260 may continue by incrementing i, to continue to attempt to calculate the trailer length D (2268). Alternatively, as shown in
where Dref is a reference trailer length having an average peak ratio Rref. Since Dref and Rref are known values, the processor solves the peak equation and sets the trailer length D to Di,peak in step 2276.
Accordingly, by utilizing the method 2260, the trailer length D may be estimated by the processor by sampling the wheel steer angle δ and the hitch angle γ, to provide a simple approximation of the trailer length when the vehicle 100 is turning.
a(t)=D sin(γ(t))
This equation may further be represented based on the rate of change of the functions γ(t) and a(t) over time, wherein V=ds/dt.
Now further substituting
the equation for {dot over (a)}(t) is expanded where ds equals the change in position of the vehicle 2102 or Vdt. The equation is then approximated by Euler's approximation to provide an estimate for {dot over (a)}(t).
From the approximation, D is modified to be represented by D(i). This modification allows the trailer length D to be estimated as a progression so D may be determined as a progression. Further, if D is determined for any two samples (e.g. i and i+1), D(i) is further substituted with D. Substituting D may provide for further simplification, but also makes the approximation susceptible to noise from a limited sample size of the inputs of the wheel steer angle δ and the hitch angle γ. From these substitutions, the estimation for the trailer length D based on a converging geometric method of calculation is derived.
The equation for Di,ConvGeo further assumes that values sampled by the processor for γi and γi+1 are not equal to zero. This estimation of the trailer length may provide further verification that the trailer length in accurately estimated and may be combined with the minimum error approach 2150, the radius of curvature approach 2190, or any other approximation method to determine the trailer length D. The estimated trailer length Di,ConvGeo may progressively approach an accurate estimate of the trailer length D over time to verify the estimated trailer length as determined from any other method for estimating the trailer length D.
D cos(γ0)−A+VΔt=D cos(γ1)
This model provides for an approximation of the trailer length based on a geometric displacement method. The geometric displacement method is based on the motion of the vehicle 2102 over time and can be approximated as the following equation.
Further, by simplifying the equation, the trailer length may be approximated as Di,DispGeo by the following equation.
This estimation of the trailer length may provide yet another method for verifying that the trailer length in accurately estimated and may be combined with the minimum error approach 2150, the radius of curvature approach 2190, or any other approximation method utilized to determine the trailer length D. The estimated trailer length Di,DispGeo provides a simple and robust approach to approximate the trailer length D. The geometric displacement method may require that the γ0 and γ1 are small, similar to the geometric convergence method and further includes the condition that the hitch angle change between samples to calculated the trailer length D without error.
Referring now to
In some embodiments, the first estimated length is estimated based on the minimum error approach 2150 by the processor (2306). The second estimated length is then calculated based on the radius of curvature 2190 (2308). Though the first estimated length and the second estimated length are calculated based on the minimum error approach 2150 and the radius of curvature 2190 in this example, any of the approaches described herein may be utilized to calculate the first estimated length and the second estimated length. With the trailer length D estimated as the first estimated length and the second estimated length, the estimated values are compared to at least one predetermined value. In the present example, the processor compares Di,min_err and Di,rad to ensure that the trailer length D is accurately estimated (2310).
The estimated lengths are compared to determine if the absolute value of difference between Di,min_err and Di,rad is less than a predetermined value, and if Di,rad is greater than or equal to a minimum trailer length. The difference between the first estimated length and the second estimated length (e.g. Di,min_err and Di,rad) may vary based on the required accuracy of the trailer length D, and may be approximately 0.1 m. The minimum trailer length may be approximately 1.8 m. If Di,min_err and Di,rad do not meet the conditions of step 2230, the method 2300 may set the trailer length D to the minimum length 1.8 m (2312). The method may then continue by incrementing i, to continue to attempt to calculate the trailer length D (2314).
If the conditions are met in step 2310, the trailer length is calculated based on a third estimation method to calculate a third estimated length. The third estimation method may include any estimation method for the trailer length D as described herein. In some implementations, the third estimation method may be calculated by the processor based on a geometric approximation Di,Geom (2316). For example, a geometric approximation method may include the converging geometric method Di,ConvGeo or the geometric displacement method DDispGeo. Once the third estimated length is calculated, the trailer length D may further be compared to a range of predetermined values to verify that the trailer length D has been accurately approximated (2318). The predetermined values may correspond to a maximum trailer length and a minimum trailer length, for example 10m and 1.8 m respectively.
If the third estimated trailer length is outside the maximum trailer length and the minimum trailer length, the trailer length D may be set to 1.8 m in step 2132. If the trailer length is with the predetermined values for the maximum and minimum length, the trailer length D may be set to the third estimated length. In some implementations, the trailer length D may be set based on a geometric approximation Di,Geom (2320). By calculating the trailer length based on a plurality of estimation methods, the method 2300 provides for further accuracy to ensure that the trailer length D is accurately estimated.
It is to be understood that variations and modifications can be made on the aforementioned structure 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.
This patent application is a continuation-in-part of U.S. patent application Ser. No. 14/294,489, which was filed on Jun. 3, 2014, entitled “TRAILER LENGTH ESTIMATION IN HITCH ANGLE APPLICATIONS,” which is a continuation-in-part of U.S. patent application Ser. No. 14/289,888, which was filed on May 29, 2014, entitled “DISPLAY SYSTEM UTILIZING VEHICLE AND TRAILER DYNAMICS,” which is a continuation-in-part of U.S. patent application Ser. No. 14/256,427, which was filed on Apr. 18, 2014, entitled “CONTROL FOR TRAILER BACKUP ASSIST SYSTEM.” U.S. patent application Ser. No. 14/294,489 is also a continuation-in-part of U.S. patent application Ser. No. 14/257,420 which was filed on Apr. 21, 2014, entitled “TRAJECTORY PLANNER FOR A TRAILER BACKUP ASSIST SYSTEM,” which is a continuation-in-part of U.S. patent application Ser. No. 14/256,427, which was filed on Apr. 18, 2014, entitled “CONTROL FOR TRAILER BACKUP ASSIST SYSTEM,” which is a continuation-in-part of U.S. patent application Ser. No. 14/249,781, which was filed on Apr. 10, 2014, entitled “SYSTEM AND METHOD FOR CALCULATING A HORIZONTAL CAMERA TO TARGET DISTANCE,” which is a continuation-in-part of U.S. patent application Ser. No. 14/188,213, which was filed on Feb. 24, 2014, entitled “SENSOR SYSTEM AND METHOD FOR MONITORING TRAILER HITCH ANGLE,” which is a continuation-in-part of U.S. patent application Ser. No. 13/847,508, which was filed on Mar. 20, 2013, entitled “HITCH ANGLE ESTIMATION.” U.S. patent application Ser. No. 14/188,213 is also a continuation-in-part of U.S. patent application Ser. No. 14/068,387, which was filed on Oct. 31, 2013, entitled “TRAILER MONITORING SYSTEM AND METHOD,” which is a continuation-in-part of U.S. patent application Ser. No. 14/059,835, which was filed on Oct. 22, 2013, entitled “TRAILER BACKUP ASSIST SYSTEM,” which is a continuation-in-part of U.S. patent application Ser. No. 13/443,743 which was filed on Apr. 10, 2012, entitled “DETECTION OF AND COUNTERMEASURES FOR JACKKNIFE ENABLING CONDITIONS DURING TRAILER BACKUP ASSIST,” which is a continuation-in-part of U.S. patent application Ser. No. 13/336,060, which was filed on Dec. 23, 2011, entitled “TRAILER PATH CURVATURE CONTROL FOR TRAILER BACKUP ASSIST,” which claims benefit from U.S. Provisional Patent Application No. 61/477,132, which was filed on Apr. 19, 2011, entitled “TRAILER BACKUP ASSIST CURVATURE CONTROL.” U.S. patent application Ser. No. 14/249,781 is also a continuation-in-part of U.S. patent application Ser. No. 14/161,832 which was filed Jan. 23, 2014, entitled “SUPPLEMENTAL VEHICLE LIGHTING SYSTEM FOR VISION BASED TARGET DETECTION,” which is a continuation-in-part of U.S. patent application Ser. No. 14/059,835 which was filed on Oct. 22, 2013, entitled “TRAILER BACKUP ASSIST SYSTEM.” Furthermore, U.S. patent application Ser. No. 14/249,781 is a continuation-in-part of U.S. application Ser. No. 14/201,130 which was filed on Mar. 7, 2014, entitled “SYSTEM AND METHOD OF CALIBRATING A TRAILER BACKUP ASSIST SYSTEM,” which is a continuation-in-part of U.S. patent application Ser. No. 14/068,387, which was filed on Oct. 31, 2013, entitled “TRAILER MONITORING SYSTEM AND METHOD.” The aforementioned related applications are hereby incorporated by reference in their entirety.
Number | Name | Date | Kind |
---|---|---|---|
3542390 | Fikes et al. | Nov 1970 | A |
3605088 | Savelli | Sep 1971 | A |
3787077 | Sanders | Jan 1974 | A |
3833928 | Gavit et al. | Sep 1974 | A |
3860257 | Mesly | Jan 1975 | A |
4040006 | Kimmel | Aug 1977 | A |
4042132 | Bohman et al. | Aug 1977 | A |
4122390 | Kollitz et al. | Oct 1978 | A |
4212483 | Howard | Jul 1980 | A |
4366966 | Ratsko et al. | Jan 1983 | A |
4735432 | Brown | Apr 1988 | A |
4752080 | Rogers | Jun 1988 | A |
4848499 | Martinet et al. | Jul 1989 | A |
4943080 | Reimer | Jul 1990 | A |
5001639 | Breen | Mar 1991 | A |
5056905 | Jensen | Oct 1991 | A |
5097250 | Hernandez | Mar 1992 | A |
5108123 | Rubenzik | Apr 1992 | A |
5108158 | Breen | Apr 1992 | A |
5132851 | Bomar et al. | Jul 1992 | A |
5152544 | Dierker, Jr. et al. | Oct 1992 | A |
5191328 | Nelson | Mar 1993 | A |
5244226 | Bergh | Sep 1993 | A |
5246242 | Penzotti | Sep 1993 | A |
5247442 | Kendall | Sep 1993 | A |
5282641 | McLaughlin | Feb 1994 | A |
5289892 | Notsu | Mar 1994 | A |
5290057 | Pellerito | Mar 1994 | A |
5455557 | Noll et al. | Oct 1995 | A |
5521633 | Nakajima et al. | May 1996 | A |
5523947 | Breen | Jun 1996 | A |
5541778 | DeFlorio | Jul 1996 | A |
5559696 | Borenstein | Sep 1996 | A |
5579228 | Kimbrough | Nov 1996 | A |
5650764 | McCullough | Jul 1997 | A |
5690347 | Juergens et al. | Nov 1997 | A |
5719713 | Brown | Feb 1998 | A |
5747683 | Gerum et al. | May 1998 | A |
5821852 | Fairchild | Oct 1998 | A |
5980048 | Rannells, Jr. et al. | Nov 1999 | A |
6042196 | Nakamura et al. | Mar 2000 | A |
6124709 | Allwine | Sep 2000 | A |
6151175 | Osha | Nov 2000 | A |
6198992 | Winslow | Mar 2001 | B1 |
6217177 | Rost | Apr 2001 | B1 |
6218828 | Bates et al. | Apr 2001 | B1 |
6223114 | Boros et al. | Apr 2001 | B1 |
6268800 | Howard | Jul 2001 | B1 |
6292094 | Deng et al. | Sep 2001 | B1 |
6472865 | Tola et al. | Oct 2002 | B1 |
6480104 | Wall et al. | Nov 2002 | B1 |
6483429 | Yasui et al. | Nov 2002 | B1 |
6494476 | Masters et al. | Dec 2002 | B2 |
6498977 | Wetzel et al. | Dec 2002 | B2 |
6568093 | Kogiso et al. | May 2003 | B2 |
6577952 | Geier et al. | Jun 2003 | B2 |
6668225 | Oh et al. | Dec 2003 | B2 |
6712378 | Austin | Mar 2004 | B1 |
6801125 | McGregor et al. | Oct 2004 | B1 |
6806809 | Lee | Oct 2004 | B2 |
6838979 | Deng et al. | Jan 2005 | B2 |
6854557 | Deng et al. | Feb 2005 | B1 |
6857494 | Kobayashi et al. | Feb 2005 | B2 |
6879240 | Kruse | Apr 2005 | B2 |
6956468 | Lee et al. | Oct 2005 | B2 |
6959970 | Tseng | Nov 2005 | B2 |
6999856 | Lee et al. | Feb 2006 | B2 |
7028804 | Eki et al. | Apr 2006 | B2 |
7032705 | Zheng et al. | Apr 2006 | B2 |
7046127 | Boddy | May 2006 | B2 |
7058493 | Inagaki | Jun 2006 | B2 |
7089101 | Fischer et al. | Aug 2006 | B2 |
7154385 | Lee | Dec 2006 | B2 |
7159890 | Craig et al. | Jan 2007 | B2 |
7170285 | Spratte | Jan 2007 | B2 |
7171330 | Kruse et al. | Jan 2007 | B2 |
7204504 | Gehring et al. | Apr 2007 | B2 |
7219913 | Atley | May 2007 | B2 |
7225891 | Gehring et al. | Jun 2007 | B2 |
7229139 | Lu et al. | Jun 2007 | B2 |
7239958 | Grougan et al. | Jul 2007 | B2 |
7269489 | Deng et al. | Sep 2007 | B2 |
7272481 | Einig et al. | Sep 2007 | B2 |
7295907 | Lu et al. | Nov 2007 | B2 |
7401871 | Lu et al. | Jul 2008 | B2 |
7405557 | Spratte et al. | Jul 2008 | B2 |
7413266 | Lenz et al. | Aug 2008 | B2 |
7425889 | Widmann et al. | Sep 2008 | B2 |
7447585 | Tandy, Jr. et al. | Nov 2008 | B2 |
7451020 | Goetting et al. | Nov 2008 | B2 |
7463137 | Wishart et al. | Dec 2008 | B2 |
7504995 | Lawrence et al. | Mar 2009 | B2 |
7540523 | Russell et al. | Jun 2009 | B2 |
7548155 | Schutt et al. | Jun 2009 | B2 |
7623952 | Unruh et al. | Nov 2009 | B2 |
7648153 | Metternich et al. | Jan 2010 | B2 |
7690737 | Lu | Apr 2010 | B2 |
7715953 | Shepard | May 2010 | B2 |
7731302 | Tandy, Jr. et al. | Jun 2010 | B2 |
7793965 | Padula | Sep 2010 | B2 |
7798263 | Tandy, Jr. et al. | Sep 2010 | B2 |
7878545 | Rhymer et al. | Feb 2011 | B2 |
7904222 | Lee et al. | Mar 2011 | B2 |
7905507 | Perri | Mar 2011 | B2 |
7950751 | Offerle et al. | May 2011 | B2 |
8010252 | Getman et al. | Aug 2011 | B2 |
8010253 | Lundquist | Aug 2011 | B2 |
8038166 | Piesinger | Oct 2011 | B1 |
8044779 | Hahn et al. | Oct 2011 | B2 |
8073594 | Lee et al. | Dec 2011 | B2 |
8157284 | McGhie et al. | Apr 2012 | B1 |
8165770 | Getman et al. | Apr 2012 | B2 |
8167444 | Lee et al. | May 2012 | B2 |
8174576 | Akatsuka et al. | May 2012 | B2 |
8180543 | Futamura et al. | May 2012 | B2 |
8190364 | Rekow | May 2012 | B2 |
8191915 | Freese, V et al. | Jun 2012 | B2 |
8192036 | Lee et al. | Jun 2012 | B2 |
8215436 | DeGrave et al. | Jul 2012 | B2 |
8223204 | Hahn | Jul 2012 | B2 |
8244442 | Craig et al. | Aug 2012 | B2 |
8260518 | Englert | Sep 2012 | B2 |
8267485 | Barlsen et al. | Sep 2012 | B2 |
8308182 | Ortmann et al. | Nov 2012 | B2 |
8326504 | Wu et al. | Dec 2012 | B2 |
8342560 | Albers et al. | Jan 2013 | B2 |
8380390 | Sy et al. | Feb 2013 | B2 |
8380416 | Offerle et al. | Feb 2013 | B2 |
8393632 | Vortmeyer et al. | Mar 2013 | B2 |
8401744 | Chiocco | Mar 2013 | B2 |
8469125 | Yu et al. | Jun 2013 | B2 |
8504243 | Kageyama | Aug 2013 | B2 |
8548680 | Ryerson et al. | Oct 2013 | B2 |
8548683 | Cebon et al. | Oct 2013 | B2 |
8576115 | Basten | Nov 2013 | B2 |
8626382 | Obradovich | Jan 2014 | B2 |
8675953 | Elwell et al. | Mar 2014 | B1 |
8755984 | Rupp et al. | Jun 2014 | B2 |
8807261 | Subrt et al. | Aug 2014 | B2 |
8833789 | Anderson | Sep 2014 | B2 |
8886400 | Kossira et al. | Nov 2014 | B2 |
8930140 | Trombley et al. | Jan 2015 | B2 |
8939462 | Adamczyk et al. | Jan 2015 | B2 |
8955865 | Fortin et al. | Feb 2015 | B2 |
9008913 | Sears et al. | Apr 2015 | B1 |
9026311 | Pieronek et al. | May 2015 | B1 |
9042603 | Elwart et al. | May 2015 | B2 |
9120358 | Motts et al. | Sep 2015 | B2 |
20010024333 | Rost | Sep 2001 | A1 |
20010037164 | Hecker | Nov 2001 | A1 |
20020128764 | Hecker et al. | Sep 2002 | A1 |
20040017285 | Zielinski et al. | Jan 2004 | A1 |
20040021291 | Haug et al. | Feb 2004 | A1 |
20040093139 | Wildey et al. | May 2004 | A1 |
20040130441 | Lee | Jul 2004 | A1 |
20050000738 | Gehring et al. | Jan 2005 | A1 |
20050128059 | Vause | Jun 2005 | A1 |
20050206225 | Offerle et al. | Sep 2005 | A1 |
20050206231 | Lu et al. | Sep 2005 | A1 |
20050236201 | Spannheimer et al. | Oct 2005 | A1 |
20050236896 | Offerle et al. | Oct 2005 | A1 |
20060041358 | Hara | Feb 2006 | A1 |
20060071447 | Gehring et al. | Apr 2006 | A1 |
20060076828 | Lu et al. | Apr 2006 | A1 |
20060103511 | Lee et al. | May 2006 | A1 |
20060111820 | Goetting et al. | May 2006 | A1 |
20060142936 | Dix | Jun 2006 | A1 |
20060244579 | Raab | Nov 2006 | A1 |
20070027581 | Bauer et al. | Feb 2007 | A1 |
20070090688 | Haemmerling et al. | Apr 2007 | A1 |
20070132560 | Nystrom et al. | Jun 2007 | A1 |
20070152424 | Deng et al. | Jul 2007 | A1 |
20070285808 | Beale | Dec 2007 | A1 |
20080143593 | Graziano et al. | Jun 2008 | A1 |
20080147277 | Lu et al. | Jun 2008 | A1 |
20080231701 | Greenwood et al. | Sep 2008 | A1 |
20080312792 | Dechamp | Dec 2008 | A1 |
20090005932 | Lee et al. | Jan 2009 | A1 |
20090079828 | Lee et al. | Mar 2009 | A1 |
20090093928 | Getman et al. | Apr 2009 | A1 |
20090198425 | Englert | Aug 2009 | A1 |
20090228182 | Waldbauer et al. | Sep 2009 | A1 |
20090248346 | Fennel et al. | Oct 2009 | A1 |
20090300701 | Karaoguz et al. | Dec 2009 | A1 |
20090306861 | Schumann et al. | Dec 2009 | A1 |
20100063702 | Sabelstrom et al. | Mar 2010 | A1 |
20100171828 | Ishii | Jul 2010 | A1 |
20100332049 | Sy et al. | Dec 2010 | A1 |
20110001825 | Hahn | Jan 2011 | A1 |
20110018231 | Collenberg | Jan 2011 | A1 |
20110022282 | Wu et al. | Jan 2011 | A1 |
20110125457 | Lee et al. | May 2011 | A1 |
20110160956 | Chung et al. | Jun 2011 | A1 |
20110257860 | Getman et al. | Oct 2011 | A1 |
20120041658 | Turner | Feb 2012 | A1 |
20120086808 | Lynam et al. | Apr 2012 | A1 |
20120095649 | Klier et al. | Apr 2012 | A1 |
20120109471 | Wu | May 2012 | A1 |
20120112434 | Albers et al. | May 2012 | A1 |
20120185131 | Headley | Jul 2012 | A1 |
20120200706 | Greenwood et al. | Aug 2012 | A1 |
20120271512 | Rupp et al. | Oct 2012 | A1 |
20120271514 | Lavoie et al. | Oct 2012 | A1 |
20120271515 | Rhode et al. | Oct 2012 | A1 |
20120283909 | Dix | Nov 2012 | A1 |
20120283910 | Lee et al. | Nov 2012 | A1 |
20130024064 | Shepard | Jan 2013 | A1 |
20130027195 | Van Wiemeersch et al. | Jan 2013 | A1 |
20130082453 | Padula | Apr 2013 | A1 |
20130158863 | Skvarce et al. | Jun 2013 | A1 |
20130179038 | Goswami | Jul 2013 | A1 |
20130207834 | Mizutani et al. | Aug 2013 | A1 |
20130226390 | Luo et al. | Aug 2013 | A1 |
20130261843 | Kossira et al. | Oct 2013 | A1 |
20130268160 | Trombley et al. | Oct 2013 | A1 |
20140005918 | Qiang | Jan 2014 | A1 |
20140025260 | McClure | Jan 2014 | A1 |
20140052337 | Lavoie et al. | Feb 2014 | A1 |
20140058614 | Trombley et al. | Feb 2014 | A1 |
20140058622 | Trombley et al. | Feb 2014 | A1 |
20140058655 | Trombley et al. | Feb 2014 | A1 |
20140058668 | Trombley et al. | Feb 2014 | A1 |
20140085472 | Lu et al. | Mar 2014 | A1 |
20140160276 | Pliefke et al. | Jun 2014 | A1 |
20140172232 | Rupp et al. | Jun 2014 | A1 |
20140183841 | Jones | Jul 2014 | A1 |
20140188344 | Lavoie | Jul 2014 | A1 |
20140188346 | Lavoie | Jul 2014 | A1 |
20140210456 | Crossman | Jul 2014 | A1 |
20140218506 | Trombley et al. | Aug 2014 | A1 |
20140218522 | Lavoie et al. | Aug 2014 | A1 |
20140222288 | Lavoie et al. | Aug 2014 | A1 |
20140236532 | Trombley et al. | Aug 2014 | A1 |
20140249691 | Hafner et al. | Sep 2014 | A1 |
20140267688 | Aich et al. | Sep 2014 | A1 |
20140267689 | Lavoie | Sep 2014 | A1 |
20140267868 | Mazzola et al. | Sep 2014 | A1 |
20140267869 | Sawa | Sep 2014 | A1 |
20140277941 | Chiu et al. | Sep 2014 | A1 |
20140277942 | Kyrtsos et al. | Sep 2014 | A1 |
20140297128 | Lavoie et al. | Oct 2014 | A1 |
20140297129 | Lavoie et al. | Oct 2014 | A1 |
20140303847 | Lavoie | Oct 2014 | A1 |
20140309888 | Smit et al. | Oct 2014 | A1 |
20140324295 | Lavoie | Oct 2014 | A1 |
20140343795 | Lavoie | Nov 2014 | A1 |
20140379217 | Rupp et al. | Dec 2014 | A1 |
20150002670 | Bajpai | Jan 2015 | A1 |
20150035256 | Klank et al. | Feb 2015 | A1 |
20150057903 | Rhode et al. | Feb 2015 | A1 |
20150066296 | Trombley et al. | Mar 2015 | A1 |
20150066298 | Sharma et al. | Mar 2015 | A1 |
20150105975 | Dunn | Apr 2015 | A1 |
20150115571 | Zhang et al. | Apr 2015 | A1 |
20150120141 | Lavoie et al. | Apr 2015 | A1 |
20150120143 | Schlichting | Apr 2015 | A1 |
20150134183 | Lavoie et al. | May 2015 | A1 |
20150138340 | Lavoie | May 2015 | A1 |
20150149040 | Hueger et al. | May 2015 | A1 |
20150158527 | Hafner et al. | Jun 2015 | A1 |
20150165850 | Chiu et al. | Jun 2015 | A1 |
20150197278 | Boos et al. | Jul 2015 | A1 |
20150203156 | Hafner et al. | Jul 2015 | A1 |
20150210254 | Pieronek et al. | Jul 2015 | A1 |
20150210317 | Hafner et al. | Jul 2015 | A1 |
20150217693 | Pliefke et al. | Aug 2015 | A1 |
20150269444 | Lameyre et al. | Sep 2015 | A1 |
Number | Date | Country |
---|---|---|
102582686 | Sep 2013 | CN |
3923676 | Jan 1991 | DE |
3931518 | Apr 1991 | DE |
9208595 | Aug 1992 | DE |
19526702 | Feb 1997 | DE |
10030738 | Aug 2001 | DE |
10031244 | Jan 2002 | DE |
10065230 | Jul 2002 | DE |
10122562 | Jul 2002 | DE |
10154612 | May 2003 | DE |
10312548 | May 2004 | DE |
10333998 | Feb 2005 | DE |
102004050149 | Apr 2006 | DE |
102005042957 | Mar 2007 | DE |
102005043467 | Mar 2007 | DE |
102005043468 | Mar 2007 | DE |
102006002294 | Jul 2007 | DE |
102006048947 | Apr 2008 | DE |
102006056408 | Jun 2008 | DE |
102008020838 | Nov 2008 | DE |
102007029413 | Jan 2009 | DE |
102008045436 | Mar 2010 | DE |
102006035021 | Apr 2010 | DE |
102008043675 | May 2010 | DE |
102009007990 | Aug 2010 | DE |
102009012253 | Sep 2010 | DE |
102009027041 | Dec 2010 | DE |
102009038552 | Feb 2011 | DE |
102010006323 | Aug 2011 | DE |
102008004158 | Oct 2011 | DE |
102008004159 | Oct 2011 | DE |
102008004160 | Oct 2011 | DE |
102010021052 | Nov 2011 | DE |
102010029184 | Nov 2011 | DE |
102010045519 | Mar 2012 | DE |
102011104256 | Jul 2012 | DE |
102011101990 | Oct 2012 | DE |
202012010517 | Dec 2012 | DE |
102011108440 | Jan 2013 | DE |
102011120814 | Jun 2013 | DE |
102012006206 | Oct 2013 | DE |
102012206133 | Oct 2013 | DE |
102012019234 | Apr 2014 | DE |
0418653 | Mar 1991 | EP |
0433858 | Jun 1991 | EP |
1361543 | Nov 2003 | EP |
1593552 | Mar 2007 | EP |
1810913 | Jul 2007 | EP |
2388180 | Nov 2011 | EP |
2452549 | May 2012 | EP |
2487454 | Aug 2012 | EP |
2551132 | Jan 2013 | EP |
2644477 | Oct 2013 | EP |
2803944 | Nov 2014 | EP |
2515379 | Apr 1983 | FR |
2265587 | Oct 1993 | GB |
2342630 | Apr 2000 | GB |
2398048 | Aug 2004 | GB |
2398049 | Aug 2004 | GB |
2398050 | Aug 2004 | GB |
61006458 | Jan 1986 | JP |
6159491 | Mar 1986 | JP |
6385568 | Jun 1988 | JP |
01095980 | Apr 1989 | JP |
01095981 | Apr 1989 | JP |
09267762 | Oct 1997 | JP |
09328078 | Dec 1997 | JP |
10001063 | Jan 1998 | JP |
11124051 | May 1999 | JP |
11278319 | Oct 1999 | JP |
2002012172 | Jan 2002 | JP |
2002068032 | Mar 2002 | JP |
2003034261 | Feb 2003 | JP |
2003148938 | May 2003 | JP |
3716722 | Nov 2005 | JP |
2008027138 | Feb 2008 | JP |
2012105158 | May 2012 | JP |
2012166647 | Sep 2012 | JP |
2014002056 | Jan 2014 | JP |
8503263 | Aug 1985 | WO |
0044605 | Aug 2000 | WO |
2005005200 | Jan 2005 | WO |
2005116688 | Dec 2005 | WO |
2006042665 | Apr 2006 | WO |
2012059207 | May 2012 | WO |
2012103193 | Aug 2012 | WO |
2014019730 | Feb 2014 | WO |
2014037500 | Mar 2014 | WO |
2014070047 | May 2014 | WO |
2014092611 | Jun 2014 | WO |
2014123575 | Aug 2014 | WO |
2015074027 | May 2015 | WO |
Entry |
---|
“Ford Super Duty: Truck Technologies”, Brochure, Sep. 2011, 2 pages. |
Kristopher Bunker, “2012 Guide to Towing”, Trailer Life, 2012, 38 pages. |
A. Gonzalez-Cantos, “Backing-Up Maneuvers of Autonomous Tractor-Trailer Vehicles using the Qualitative Theory of Nonlinear Dynamical Systems,” International Journal of Robotics Research, Jan. 2009, vol. 28, 1 page. |
L. Chu, Y. Fang, M. Shang, J. Guo, F. Zhou, “Estimation of Articulation Angle for Tractor Semi-Trailer Based on State Observer”, ACM Digital Library, ICMTMA '10 Proceedings of the 2010 International Conference on Measuring Technology and Automation, vol. 2, Mar. 2010, 1 page. |
M. Wagner, D. Zoebel, and A. Meroth, “Adaptive Software and Systems Architecture for Driver Assistance Systems” International Journal of Machine Learning and Computing, Oct. 2011, vol. 1, No. 4, 7 pages. |
F.W. Kienhöfer; D. Cebon, “An Investigation of ABS Strategies for Articulated Vehicles”, Cambridge University, Engineering Department, United Kingdom, date unknown, 13 pages. |
C. Lundquist; W. Reinelt; O. Enqvist, “Back Driving Assistant for Passenger Cars with Trailer”, ZF Lenksysteme GmbH, Schwäbisch Gmünd, Germany, 2006 (SAE Int'l) Jan. 2006, 8 pages. |
Zhe Leng; Minor, M., “A Simple Tractor-Trailer Backing Control Law for Path Following”, IEEE, Intelligent Robots and Systems (IROS) IEEE/RSJ International Conference, Oct. 2010, 2 pages. |
Kinjo, H.; Maeshiro, M.; Uezato, E.; Yamamoto, T., “Adaptive Genetic Algorithm Observer and its Application to Trailer Truck Control System”, IEEE, SICE-ICASE International Joint Conference, Oct. 2006, 2 pgs. |
J. Roh; H. Lee; W. Chung, “Control of a Car with a Trailer Using the Driver Assistance System”, IEEE, International Conference on Robotics and Biomimetics; Phuket, Thailand, Dec. 2011, 6 pages. |
A. Gonzalez-Cantos; J.I. Maza; A. Ollero, “Design of a Stable Backing Up Fuzzy Control of Autonomous Articulated Vehicles for Factory Automation”, Dept. of Systems Engineering and Automatic Control, University of Seville, Spain, 2001, 5 pages. |
Altafini, C.; Speranzon, A.; Wahlberg, B., “A Feedback Control Scheme for Reversing a Truck and Trailer Vehicle”, IEEE, Robotics and Automation, IEEE Transactions, Dec. 2001, vol. 17, No. 6, 2 pages. |
Zare, A. Sharafi; M. Kamyad, A.V., “A New Approach in Intelligent Trailer Parking”, IEEE, 2010 2nd International Mechanical and Electrical Technology (ICMET), Sep. 2010, 1 page. |
Tanaka, K.; Sano, M., “A Robust Stabilization Problem of Fuzzy Control Systems and its Application to Backing up Control of a Truck-trailer”, IEEE Transactions on Fuzzy Systems, May 1994, vol. 2, No. 2, 1 page. |
Sharafi, M. Zare; A. Kamyad; A.V. Nikpoor, S., “Intelligent Parking Method for Truck in Presence of Fixed and Moving Obstacles and Trailer in Presence of Fixed Obstacles: Advanced Fuzzy Logic Technologies in Industrial Applications”, IEEE, 2010 International Electronics and Information Engineering (ICEIE), Aug. 2010, vol. 2, 1 page. |
Hodo, D. W.; Hung, J.Y.; Bevly, D. M.; Millhouse, S., “Effects of Sensor Placement and Errors on Path Following Control of a Mobile Robot-Trailer System”, IEEE, American Control Conference, Jul. 2007, 1 page. |
Sharafi, M. Zare; A. Kamyad; A.V. Nikpoor, S., “Intelligent Parking Method for Trailers in Presence of Fixed and Moving Obstacles”, IEEE, 2010 3rd International Conference on Advanced Computer Theory and Engineering (ICACTE), Aug. 2010, vol. 6, 1 page. |
Chieh Chen; Tomizuka, M., “Steering and Independent Braking Control for Tractor-Semitrailer Vehicles in Automated Highway Systems”, IEEE, Proceedings of the 34th IEEE Conference on Decision and Control, Dec. 1995, vol. 2, 1 page. |
P. Bolzern, R.M. Desantis, A. Locatelli, “An Input-Output Linearization Approach to the Control of an n-Body Articulated Vehicle”, J. Dyn. Sys., Meas., Control, Sep. 2001, vol. 123, No. 3, 3 pages. |
Dieter Zöbel, David Polock, Philipp Wojke, “Steering Assistance for Backing Up Articulated Vehicles”, Systemics, Cybernetics and Informatics; vol. 1, No. 5, 6 pages, no date provided. |
J.R. Billing; J.D. Patten; R.B. Madill, “Development of Configurations for Infrastructure-Friendly Five- and Six-Axle SemiTrailers”, National Research Council of Canada and Ontario Ministry of Transportation, 11 pages., no date provided. |
Jesus Morales, Anthony Mandow, Jorge L. Martinez, and Alfonso Garcia-Cerezo, “Driver Assistance System for Backward Maneuvers in Passive Multi-Trailer Vehicles”, IEEE/RSJ International Conference on Intelligent Robots and Systems (IROS), Oct. 2012, 7 pages. |
Cedric Pradalier and Kane Usher, “Experiments in Autonomous Reversing of a Tractor-Trailer System”, 6th International Conference on Field and Service Robotics, inria-00195700, Version 1, Dec. 2007, 10 pages. |
Andri Riid, Alar Leibak, Ennu Rüstern, “Fuzzy Backing Control of Truck and Two Trailers”, Tallinn University of Technology; Tallinn, Estonia, no date provided, 6 pages. |
Jane McGrath, “How to Avoid Jackknifing”, A Discovery Company, 3 pages. |
Claudio Altafini, Alberto Speranzon, and Karl Henrik Johansson, “Hybrid Control of a Truck and Trailer Vehicle”, Springer-Verlag Berlin Heidelberg, HSCC 2002, LNCS 2289; 2002, 14 pages. |
Jujnovich, B.; Roebuck, R.; Odhams, A.; David, C., “Implementation of Active Rear Steering of a Tractor Semitrailer”, Cambridge University, Engineering Department; Cambridge, United Kingdom, no date provided, 10 pages. |
A.M.C. Odhams; R.L. Roebuck; C. Cebon, “Implementation of Active Steering on a Multiple Trailer Long Combination Vehicle”, Cambridge University, Engineering Department; Cambridge, United Kingdom, no date provided, 13 pages. |
Cedric Pradalier and Kane Usher, “Robust Trajectory Tracking for a Reversing Tractor-Trailer System”, (Draft), Field and Service Robotics Conference, CSIRO ICT Centre, Jul. 2007, 16 pages. |
Stahn, R.; Heiserich, G.; Stopp, A., “Laser Scanner-Based Navigation for Commercial Vehicles”, IEEE, 2007 IEEE Intelligent Vehicles Symposium, Jun. 2007, 1 page. |
Lee Yong H.; Weiwen Deng; Chin Yuen-Kwok Steve; McKay Neil, “Feasibility Study for a Vehicle-Trailer Backing Up Control”, Refdoc.fr, SAE Transactions, 2004, vol. 113, No. 6, 1 page. |
A.M.C. Odhams; R.L. Roebuck; B.A. Jujnovich; D. Cebon, “Active Steering of a Tractor- Semi- Trailer” Proceedings of the Institution of Mechanical Engineers, Part D: Journal of Automobile Engineering, SAGE Journals, Feb. 2010, vol. 225, No. 7, 1 page. |
Haviland, G S, “Automatic Brake Control for Trucks—What Good Is It?”, TRID, Society of Automotive Engineers, Sep. 1968, 1 page. |
William E. Travis; David W. Hodo; David M. Bevly; John Y. Hung, “UGV Trailer Position Estimation Using a Dynamic Base RTK System”, American Institute of Aeronautics and Astronautics, 12 pages, no date provided. |
“VSE Electronic Trailer Steering”, ETS for Trailers, version 2009, VSE Trailer Systems B.V., 28 pages. |
“Telematics Past, Present, and Future,” Automotive Service Association, www.ASAshop.org, May 2008, 20 pages. |
“Fully Automatic Trailer Tow Hitch With LIN Bus,” https://webista.bmw.com/webista/show?id=1860575499&lang=engb&print=1, no date provided, 5 pages. |
“VBOX Yaw Rate Sensor With Integral Accelerometers,” Racelogic, www.racelogic.co.uk, no date provided, 2 pages. |
P.D.C.R Jayarathna; J.V Wijayakulasooriya; S.R Kodituwakku, “Fuzzy Logic and Neural Network Control Systems for Backing up a Truck and a Trailer”, International Journal of Latest Trends in Computing, Sep. 2011, vol. 2, No. 3, 8 pages. |
Olof Enqvist, “AFS-Assisted Trailer Reversing,” Institutionen för systemteknik Deartment of Electrical Engineering, Jan. 27, 2006, 57 pages. |
Novak, Domen; Dovzan, Dejan; Grebensek, Rok; Oblak, Simon, “Automated Parking System for a Truck and Trailer”, International Conference on Advances in the Internet, Processing, Systems and Interdisciplinary Research, Florence, 2007, WorldCat.org, 13 pgs. |
SH. Azadi, H.R. Rezaei Nedamani, and R. Kazemi, “Automatic Parking of an Articulated Vehicle Using ANFIS”, Global Journal of Science, Engineering and Technology (ISSN: 2322-2441), 2013, pp. 93-104, Issue No. 14. |
F. Cuesta and A. Ollero, “Intelligent System for Parallel Parking of Cars and Tractor-Trailers”, Intelligent Mobile Robot Navigation, STAR, 2005, pp. 159-188, Springer-Verlag Berlin Heidelberg. |
Number | Date | Country | |
---|---|---|---|
20140297128 A1 | Oct 2014 | US |
Number | Date | Country | |
---|---|---|---|
61477132 | Apr 2011 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 14294489 | Jun 2014 | US |
Child | 14301919 | US | |
Parent | 14289888 | May 2014 | US |
Child | 14294489 | US | |
Parent | 14256427 | Apr 2014 | US |
Child | 14289888 | US | |
Parent | 14294489 | US | |
Child | 14289888 | US | |
Parent | 14257420 | Apr 2014 | US |
Child | 14294489 | US | |
Parent | 14256427 | US | |
Child | 14257420 | US | |
Parent | 14249781 | Apr 2014 | US |
Child | 14256427 | US | |
Parent | 14188213 | Feb 2014 | US |
Child | 14249781 | US | |
Parent | 13847508 | Mar 2013 | US |
Child | 14188213 | US | |
Parent | 14068387 | Oct 2013 | US |
Child | 13847508 | US | |
Parent | 14059835 | Oct 2013 | US |
Child | 14068387 | US | |
Parent | 13443743 | Apr 2012 | US |
Child | 14059835 | US | |
Parent | 13336060 | Dec 2011 | US |
Child | 13443743 | US | |
Parent | 14249781 | US | |
Child | 13443743 | US | |
Parent | 14161832 | Jan 2014 | US |
Child | 14249781 | US | |
Parent | 14059835 | US | |
Child | 14161832 | US | |
Parent | 14249781 | US | |
Child | 14161832 | US | |
Parent | 14201130 | Mar 2014 | US |
Child | 14249781 | US | |
Parent | 14068387 | US | |
Child | 14201130 | US |