US 10,155,478 B2Grant

Centerline method for trailer hitch angle detection

Issue Date:2018-12-18

•14 Claims

•17 Drawing Sheets

Abstract

A system for detecting a hitch angle between a vehicle and a trailer is provided herein. An imaging device is configured to capture images of the trailer and a controller is configured to process the captured images. The controller derives an edge map and identifies trailer pixels therein. The controller defines a number of candidate lines in the edge map and determines the hitch angle based on an angle between a selected candidate line and a reference line.

Metadata

Assignee

Ford Global Technologies, LLC

Inventors

Zheng Hu
Erick Michael Lavoie

Application Information

Application Number:US 14/972,885

Filing Date:2015-12-17

Priority Date:2015-12-17

Art Unit:2485

Classifications

IPC:

G06T7/60B60R1/00G06T7/00

Field of Search:

B60R 1/00G06T 7/004

Patent Drawings (17 sheets)

Description

Field of the Invention

[0001] The present invention generally relates to trailer backup assist systems, and more particularly, to trailer backup assist systems employing hitch angle detection through image processing.

Background of the Invention

[0002] Reversing a vehicle while towing a trailer can be challenging for many drivers, particularly for drivers that drive with a trailer on an infrequent basis or with various types of trailers. Some systems used to assist a driver in backing a trailer rely on hitch angle measurements to determine the position of the trailer relative to the vehicle. Thus, the accuracy and reliability of the hitch angle measurements can be critical to the operation of the trailer backup assist system.

Summary of the Invention

[0003] According to one aspect of the present invention, a system for detecting a hitch angle between a vehicle and a trailer is provided. An imaging device is configured to capture images of the trailer and a controller is configured to process the captured images. The controller derives an edge map and identifies trailer pixels therein. The controller defines a number of candidate lines in the edge map and determines the hitch angle based on an angle between a selected candidate line and a reference line.

[0004] According to another aspect of the present invention, a method of detecting a hitch angle between a vehicle and a trailer is provided. The method includes the steps of capturing images of the trailer using an imaging device and providing a controller for processing the captured images. The controller derives an edge map and identifies trailer pixels therein. The controller generates a number of candidate lines in the edge map and determines the hitch angle based on an angle between a selected candidate line and a reference line.

[0005] These and other features, advantages, and objects of the present invention will be further understood and appreciated by those skilled in the art by reference to the following specification, claims, and appended drawings.

Brief Description of the Drawings

[0006] In the drawings:

[0007] FIG. 1 is a top perspective view of a vehicle attached to a trailer with one embodiment of a hitch angle sensor for operating a trailer backup assist system;

[0008] FIG. 2 is a block diagram illustrating one embodiment of the trailer backup assist system having a steering input device, a curvature controller, and a trailer braking system;

[0009] FIG. 3 is a flow diagram of a method of detecting a hitch angle, according to one embodiment;

[0010] FIG. 4 is a captured image showing a trailer in straight alignment with a vehicle and the presence of ground noise;

[0011] FIG. 5 is an edge map of the captured image shown in FIG. 4;

[0012] FIG. 6 illustrates the blurring of ground noise in an averaged image;

[0013] FIG. 7 is an edge map of the averaged image shown in FIG. 6;

[0014] FIG. 8 illustrates a trailer contour of a template image;

[0015] FIG. 9 illustrates a template image being matched to a search image to determine a hitch angle;

[0016] FIG. 10 is a search image having a proximity zone for jackknife detection and a number of candidate hitch point locations about which a template image can be rotated to determine an actual imaged hitch point and a hitch angle;

[0017] FIG. 11 is a flow diagram of a method of detecting a hitch angle, according to another embodiment;

[0018] FIG. 12 is an edge map of a captured image showing a number of candidate lines, one of which, is selected to determine a hitch angle based on its angular position relative to a reference line;

[0019] FIG. 13 is a flow diagram of a method of locating an imaged hitch point, according to one embodiment;

[0020] FIGS. 14 and 15 are each captured images in which a trailer appears at a distinct hitch angle and a detection window is used to scan an imaged drawbar to locate an imaged hitch point;

[0021] FIG. 16 is a graph illustrating averaged pixel differences for a number of pixel positions common to the captured images shown in FIGS. 14 and 15;

[0022] FIG. 17 is a kinematic model of the vehicle and trailer shown in FIG. 1;

[0023] FIG. 18 is a flow diagram of a method of detecting a hitch angle, according to yet another embodiment; and

[0024] FIG. 19 is a flow diagram of a method of initializing hitch angle detection, according to one embodiment.

Detailed Description of the Preferred Embodiments

[0025] For purposes of description herein, it is to be understood that the disclosed trailer backup assist system and the related methods may assume various alternative embodiments and orientations, except where expressly specified to the contrary. It is also to be understood that the specific devices and processes illustrated in the attached drawings, and described in the following specification, are simply exemplary embodiments of the inventive concepts defined in the appended claims. While various aspects of the trailer backup assist system and the related methods are described with reference to a particular illustrative embodiment, the disclosed invention is not limited to such embodiments, and additional modifications, applications, and embodiments may be implemented without departing from the disclosed invention. Hence, specific dimensions and other physical characteristics relating to the embodiments disclosed herein are not to be considered as limiting, unless the claims expressly state otherwise.

[0026] As used herein, the term “and/or,” when used in a list of two or more items, means that any one of the listed items can be employed by itself, or any combination of two or more of the listed items can be employed. For example, if a composition is described as containing components A, B, and/or C, the composition can contain A alone; B alone; C alone; A and B in combination; A and C in combination; B and C in combination; or A, B, and C in combination.

[0027] Referring to FIGS. 1 and 2, reference numeral 10 generally designates a trailer backup assist system for controlling a backing path of a trailer 12 attached to a vehicle 14 by allowing a driver of the vehicle 14 to specify a desired curvature of the backing path of the trailer 12. The vehicle 14 is embodied as a pickup truck that is pivotally attached to one embodiment of the trailer 12 that has a box frame 16 with an enclosed cargo area 18, a single axle 20 operably coupled to wheels 22 and 24, and a tongue 26 longitudinally extending forward from the enclosed cargo area 18. The illustrated trailer 12 also has a trailer hitch connector in the form of a coupler assembly 28 that is connected to a vehicle hitch connector in the form of a hitch ball 30 and drawbar 31. The coupler assembly 28 latches onto the hitch ball 30 to provide a pivoting hitch point 32 that allows for articulation of a hitch angle between the vehicle 14 and the trailer 12. As defined herein, the hitch angle corresponds to the angle formed between the center longitudinal axis of the vehicle 14 and of the trailer 12 (see hitch angle γ; FIG. 17). It should be appreciated that additional embodiments of the trailer 12 may alternatively couple with the vehicle 14 to provide a pivoting connection, such as by connecting with a fifth wheel connector. It is also contemplated that additional embodiments of the trailer 12 may include more than one axle and may have various shapes and sizes configured for different loads and items, such as a boat trailer or a flatbed trailer.

[0028] The trailer backup assist system 10 also includes an imaging device 34 located at the rear of the vehicle 14 and configured to image a rear-vehicle scene. The imaging device 34 may be centrally located at an upper region of a vehicle tailgate 35 such that the imaging device 34 is elevated relative to the tongue 26 of the trailer 12. The imaging device 34 has a field of view 36 located and oriented to capture one or more images that may include the tongue 26 of the trailer 12 and the hitch ball 30, among other things. Captured images are supplied to a controller 38 of the trailer backup assist system 10 and are processed by the controller 38 to determine the hitch angle between the vehicle 14 and the trailer 12, as will be described in greater detail herein. The controller 38 is configured with a microprocessor 40 and/or other analog and/or digital circuitry for processing one or more logic routines stored in a memory 42. The logic routines may include one or more hitch angle detection routines 44 and an operating routines 46. Information from the imaging device 34 or other components of the trailer backup assist system 10 can be supplied to the controller 38 via a communication network of the vehicle 14, which can include a controller area network (CAN), a local interconnect network (LIN), or other conventional protocols used in the automotive industry. It should be appreciated that the controller 38 may be a stand-alone dedicated controller or may be a shared controller integrated with the imaging device 34 or other component of the trailer backup assist system 10 in addition to any other conceivable onboard or off-board vehicle control systems.

[0029] With respect to the present embodiment, the controller 38 of trailer backup assist system 10 may be configured to communicate with a variety of vehicle equipment. The trailer backup assist system 10 may include a vehicle sensor module 48 that monitors certain dynamics of the vehicle 14. The vehicle sensor module 48 may generate a plurality of signals that are communicated to the controller 38 and may include a vehicle speed signal generated by a speed sensor 50 and a vehicle yaw rate signal generated by a yaw rate sensor 52. A steering input device 54 may be provided to enable a driver to control or otherwise modify the desired curvature of the backing path of the trailer 12. The steering input device 54 may be communicatively coupled to the controller 38 in a wired or wireless manner and provides the controller 38 with information defining the desired curvature of the backing path of the trailer 12. In response, the controller 38 processes the information and generates corresponding steering commands that are supplied to a power assist steering system 56 of the vehicle 14. In one embodiment, the steering input device 54 includes a rotatable knob 58 operable between a number of rotated positions that each provide an incremental change to the desired curvature of the backing path of the trailer 12.

[0030] According to one embodiment, the controller 38 of the trailer backup assist system 10 may control the power assist steering system 56 of the vehicle 14 to operate the steered wheels 60 of the vehicle 14 for moving the vehicle 14 in such a manner that the trailer 12 reacts in accordance with the desired curvature of the backing path of the trailer 12. The power assist steering system 56 may be an electric power-assisted steering (EPAS) system that includes an electric steering motor 62 for turning the steered wheels 60 to a steering angle based on a steering command generated by the controller 38, whereby the steering angle may be sensed by a steering angle sensor 64 of the power assist steering system 56 and provided to the controller 38. The steering command may be provided for autonomously steering the vehicle 14 during a backup maneuver and may alternatively be provided manually via a rotational position (e.g., a steering wheel angle) of a steering wheel 66 or the rotatable knob 58. However, in some embodiments, the steering wheel 66 of the vehicle 14 may be mechanically coupled with the steered wheels 60 of the vehicle 14, such that the steering wheel 66 moves in concert with steered wheels 60 via an internal torque, thereby preventing manual intervention with the steering wheel 66 during autonomous steering of the vehicle 14. In such instances, the power assist steering system 56 may include a torque sensor 68 that senses torque (e.g., gripping and/or turning) on the steering wheel 66 that is not expected from autonomous control of the steering wheel 68 and therefore indicative of manual intervention by the driver. In some embodiments, external torque applied to the steering wheel 66 may serve as a signal to the controller 38 that the driver has taken manual control and for the trailer backup assist system 10 to discontinue autonomous steering functionality.

[0031] The controller 38 of the trailer backup assist system 10 may also communicate with a vehicle brake control system 70 of the vehicle 14 to receive vehicle speed information such as individual wheel speeds of the vehicle 14. Additionally or alternatively, vehicle speed information may be provided to the controller 38 by a powertrain control system 72 and/or the speed sensor 50, among other conceivable means. It is conceivable that individual wheel speeds may be used to determine a vehicle yaw rate, which can be provided to the controller 38 in the alternative, or in addition to, the vehicle yaw rate measured by yaw rate sensor 52 of the vehicle sensor module 48. In some embodiments, the controller 38 may provide braking commands to the vehicle brake control system 70, thereby allowing the trailer backup assist system 10 to regulate the speed of the vehicle 14 during a backup maneuver of the trailer 12. It should be appreciated that the controller 38 may additionally or alternatively regulate the speed of the vehicle 14 via interaction with the powertrain control system 72.

[0032] Through interaction with the power assist steering system 56, the vehicle brake control system 70, and/or the powertrain control system 72 of the vehicle 14, the potential for unacceptable trailer backup conditions can be reduced. Examples of unacceptable trailer backup conditions include, but are not limited to, a vehicle over-speed condition, a high hitch angle rate, hitch angle dynamic instability, a trailer jackknife condition, sensor failure, and the like. In such circumstances, the driver may be unaware of the failure until the unacceptable trailer backup condition is imminent or already happening. Therefore, it is disclosed herein that the controller 38 of the trailer backup assist system 10 can generate an alert signal corresponding to a notification of an actual, impending, and/or anticipated unacceptable trailer backup condition, and prior to driver intervention, generate a counter measure to prevent such an unacceptable trailer backup condition.

[0033] According to one embodiment, the controller 38 may communicate with one or more devices, including a vehicle alert system 74, which may prompt visual, auditory, and tactile warnings. For instance, vehicle brake lights 76 and vehicle emergency flashers may provide a visual alert and a vehicle horn 78 and/or speaker 80 may provide an audible alert. Additionally, the controller 38 and/or vehicle alert system 74 may communicate with a human machine interface (HMI) 82 of the vehicle 14. The HMI 82 may include a touchscreen vehicle display 84 such as a center-stack mounted navigation or entertainment display capable of displaying images indicating the alert. Such an embodiment may be desirable to notify the driver of the vehicle 14 that an unacceptable trailer backup condition is afoot. Further, it is contemplated that the controller 38 may communicate via wireless communication with one or more electronic portable devices such as portable electronic device 86, which is embodied as a smartphone. The portable electronic device 86 may include a display 88 for displaying one or more images and other information to a user. In response, the portable electronic device 86 may provide feedback information, such as visual, audible, and tactile alerts.

[0034] Referring to FIG. 3, a method of detecting hitch angle is illustrated. The method, also referred to herein as “the template matching method,” may be executed by the controller 38 of the trailer backup assist system 10 and is shown as one embodiment of the hitch angle detection routine 44. The template matching method generally includes processing image information to distinguish trailer contour from ground noise in images captured by the imaging device 34. The trailer contour then serves as a template and is matched to a search image to determine the hitch angle between the vehicle 14 and the trailer. 12

[0035] For purposes of illustration, a captured image 90 is exemplarily shown in FIG. 4 illustrating the trailer 12 in straight alignment with the vehicle 14 and the presence of ground noise. As defined herein, ground noise generally corresponds to any ground structure capable of interfering with image acquisition of the trailer 12. With respect to the captured image 90, potential ground noise candidates may include large stones (e.g., stone 92) and irregular ground surfaces (e.g., ground surface 94). As such, it may be difficult to accurately identify the trailer 12 when an image acquisition technique, namely edge detection, is applied to the captured image 90, as exemplarily shown in FIG. 5. With these things in mind, the template matching method described herein is able to blur out ground noise to enable identification of one or more trailer contours. Once identified, the trailer contour(s) may be stored as a template image that is matched to a search image to determine the hitch angle between the vehicle 14 and the trailer 12. In practice, the method has been found highly robust and benefits from relatively fast and straightforward computations.

[0036] The template matching method may begin at step 100, where the driver or other occupant initiates the trailer backup assist system 10. This may be achieved via user-input made through the display 84 of the vehicle 14 or other conceivable means. At step 110, the driver is instructed to pull the trailer 12 in a straight direction such that the hitch angle between the vehicle 14 and the trailer 12 is substantially zero. While the vehicle 14 and trailer 12 are engaged in the straight pull maneuver, the controller 38 derives an averaged image of all images captured by the imaging device 34 during a period of time at step 120. It has been discovered that 1-3 seconds typically suffices. Notably, the trailer 12 appears stationary within the images captured by the imaging device 34 whereas ground noise constantly changes from image to image. Thus, with respect to the averaged image, pixels associated with the trailer 12 will keep their contrast whereas pixels associated with ground noise will be blurred. To illustrate this effect, an averaged image 125 is exemplarily shown in FIG. 6.

[0037] At step 130, the controller 38 derives an edge map of the averaged image by calculating the intensity gradient for each pixel of the averaged image 125. The intensity gradient, or edge value, of each pixel may range from 0 to 255. For purposes of illustration, an edge map 135 is exemplarily shown in FIG. 7, in which the edge values of pixels associated with ground noise have been substantially weakened due to the blurring effect. At step 140, the controller 38 compares the edge value of each pixel of the edge map 135 to a threshold value (e.g., 30). Pixels having an edge value meeting or exceeding the threshold value are identified as trailer pixels whereas pixels having an edge value not meeting or exceeding the threshold value are identified as ground noise pixels. Once the trailer pixels have been identified, the controller 38 determines one or more trailer contours at step 150. The trailer contour(s) are saved to the memory 42 of the controller 38 as a template image at step 160 and may include a substantial entirety of the imaged trailer 12 or portions thereof. For purposes of illustration, a trailer contour 152 is shown in FIG. 8. As shown, the trailer contour 152 has a square shape, which is generally more computationally efficient. In its current position, the trailer contour 152 may serve as a zero hitch angle reference and enables the hitch angle between the vehicle 14 and the trailer 12 to be determined in subsequent images (i.e., search images) via template matching at step 170.

[0038] According to one embodiment, as shown in FIG. 9, the hitch angle between the vehicle 14 and the trailer 12 may be determined based on a positional relationship between a template image 158 and a search image 171. More specifically, the hitch angle may be determined by superimposing the template image 158 over the search image 171 such that the template image 158 is initially in a zero hitch angle position and subsequently rotating the template image 158 about a rotation point, preferably the imaged hitch point 172. The direction of rotation can be predicted based on information received from the steering angle sensor 64 or other sensors from which an initial assessment can be made concerning the angular position of the trailer 12 relative to the vehicle 14. Once the template image 158 has been matched to the search image 171, the angle θ at which the template image 158 is rotated relative to the zero hitch angle position can be correlated to the hitch angle between the vehicle 14 and the trailer 12.

[0039] According to one embodiment, the imaged hitch point 172 may be determined through process of elimination. For instance, as exemplarily shown in FIG. 10, the controller 38 may define a number of candidate hitch point locations 173a-173d that are positioned along a reference line 174 that extends vertically across the middle column of the search image 171. The reference line 174 is defined by the controller 38 and is assumed to coincide with the center longitudinal axis of an imaged drawbar 175 and intersect with the hitch point 172 of the imaged vehicle 14 and trailer 12. The candidate hitch point locations 173a-173d are shown evenly spaced along the reference line 174 but may vary in number and spacing in other embodiments. Once the template image 158 has been derived and the vehicle 14 and trailer 12 are moving along a curved path, the controller 38 may superimpose the template image 158 onto the search image 171 at the zero hitch angle position and rotate the template image 158 about each of the candidate hitch point locations 173a-173d in an attempt to match the template image 158 with the search image 171. Based on the match quality, a confidence score is given to each candidate hitch point location 173a-173d and the candidate hitch point location 173a-173d receiving the highest confidence score is selected as the hitch point. In the event the matching quality associated with each candidate hitch point location 173a-173d is below a predetermined threshold, the controller 38 may define additional candidate hitch point locations (not shown) along the reference line 174 in either or both directions of the candidate hitch point location 173a-173d that received the highest confidence score and execute template matching with respect to each of the additional candidate hitch point locations. This process may be iterated as many times as needed until the predetermined threshold has been met. In so doing, the location of the candidate hitch point location that is ultimately selected as the imaged hitch point will closely mirror the location of the actual hitch point 172.

[0040] While matching the template image 158 to the search image 171, the controller 38 may additionally determine the presence of an imminent jackknife scenario at step 180. With continued reference to FIG. 10, the displacement of the template image 158 may be monitored relative to a proximity zone 182 while the template image 158 is rotated about the rotation point. In the illustrated embodiment, the proximity zone 182 may be defined as the space between an imaged rear bumper 184 of the vehicle 14 and a boundary line 186 that is defined by the controller 38 and overlaid onto the search image 171. The boundary line 186 may be v-shaped and includes a pair of straight segments 188 extending outwardly at an angle from a point 189 that is located on the reference line 174 and is disposed between the imaged hitch point 172 and the imaged rear bumper 184. It should be appreciated that the boundary line 186 may assume other shapes in alternative embodiments. The location and shape of the boundary line 186 may be determined based on various considerations such as, but not limited to, vehicle speed, trailer length, drawbar length, imager characteristics, trailer contour, and vehicle contour. It is generally assumed that vehicle speed, trailer length, drawbar length, and image characteristics are known or may be otherwise measured and inputted to the trailer backup assist system 10. Vehicle contour, such as that of the imaged rear bumper 184, may be programmed at the factory.

[0041] In the event the template image 158 crosses into the proximity zone 182 of the search image 171, the controller 38 determines that an imminent jackknife scenario is present and initiates a jackknife countermeasure at step 190. Otherwise, if it is determined that an imminent jackknife scenario is not present, the controller 38 may continue to determine the hitch angle between the vehicle 14 and the trailer 12, as discussed previously with respect to step 170. The jackknife countermeasure may include generating an auditory warning via the vehicle alert system 74, generating a visual warning via the display 84, generating a braking command to the vehicle brake control system 70, reducing the torque of the powertrain control system 72, modifying the steering angle of the vehicle 14, or a combination thereof in addition to any other conceivable countermeasures. Since the trailer 12 will likely be in motion upon the controller 38 determining that an imminent jackknife scenario is present, it is generally desirable to locate and dimension the proximity zone 182 in a manner that provides sufficient time for a jackknife scenario to be detected and a countermeasure to be implemented, thereby minimizing the potential of an actual jackknifing and/or collision between the trailer 12 and the vehicle 14. Doing so also overcomes any response latency that may be inherent in the trailer backup assist system 10. While steps 170 and 180 have been illustrated in a linear fashion, it should be appreciated that both steps may be performed simultaneously.

[0042] Referring to FIG. 11, another method of detecting hitch angle is illustrated. The method, also referred to herein as “the centerline method,” may be executed by the controller 38 of the trailer backup assist system 10 and is exemplarily shown as one embodiment of the hitch angle detection routine 44. The centerline method also utilizes image information obtained by processing images captured by the imaging device 34 to determine the hitch angle between the vehicle 14 and the trailer 12. The centerline method differs from the template matching method in that the vehicle 14 and the trailer 12 need not be moving a straight direction prior to hitch angle detection, thus making the centerline method particularly useful in instances where no template image is available for the trailer 12 and the driver is prevented from pulling the trailer 12 in a straight line. When compared to the template matching method, the centerline method generally benefits from faster processing times, but is also generally less reliable. Therefore, it can be said that the centerline method provides a quick start to hitch angle detection and may be replaced at a later time by the template matching method or other suitable methods providing more reliable hitch angle measurements. Thus, for purposes of illustration, the centerline method will be described in greater detail below under the condition that no template image is available and that the vehicle 14 and trailer 12 are initially moving along a curved path.

[0043] The centerline method may begin at step 200, where the controller 38 processes successive images captured by the imaging device 34 to derive an averaged image. At step 210, the controller 38 derives an edge map by calculating an intensity gradient, or edge value, for each pixel in the averaged image. At step 220, the controller 38 identifies trailer pixels in the edge map by comparing the edge value of each pixel to a threshold value and selecting only those pixels meeting or exceeding the threshold value to correspond to trailer pixels. For purposes of illustration, an edge map 222 is exemplarily shown in FIG. 12, wherein one embodiment of the imaged trailer 12 appears slightly blurred as a result of angular displacement of the trailer 12 relative to the vehicle 14. It is contemplated that additional threshold values may be used to differentiate between trailer pixels and vehicle pixels since vehicle pixels will generally have a higher degree of contrast relative to trailer pixels due to the blurring of the trailer 12. At step 230, the controller 38 defines a number of candidate lines on the edge map 222, as exemplarily shown in FIG. 12. The candidate lines project outwardly from a common projection point, preferably the imaged hitch point 232. The direction at which the candidate lines project may vary based on a width of the rear bumper of the vehicle 14, a length of the drawbar of the vehicle 14, and a length of the tongue of the trailer 12. In the illustrated embodiment, the candidate lines may vary from −90 degrees to 90 degrees with respect to a reference line 234 that is indicative of a predetermined hitch angle (e.g., a zero hitch angle) and extends vertically across the middle column of the edge map 222 and intersects the imaged hitch point 232. While the exact location of the imaged hitch point 232 may be unknown initially, the controller 38 may assign a default projection point from which to project the candidate lines. Since it's assumed the hitch point 232 will typically be located along the reference line 234 and usually falls within a predictable range (e.g., 10-20 centimeters from the rear bumper of the vehicle 14), the selection of a default projection point meeting the foregoing criteria is generally sufficient for the purposes of initial hitch angle detection.

[0044] At step 240, the controller 38 selects the candidate line (e.g., candidate line 242) having approximately the same number of trailer pixels on each of its sides, or said differently, the candidate line, or centerline, about which the trailer pixels are substantially symmetric. Once the controller 38 has made a candidate line selection, the controller 38 may determine the hitch angle between the vehicle 14 and the trailer 12 based on the angular position of the selected candidate line 242 relative to the reference line 234 at step 250. More specifically, the angle θ between the selected candidate line 242 and the reference line 234 can be correlated to the hitch angle between the vehicle 14 and the trailer 12. As the vehicle 14 and trailer 12 continue along its course, steps 200-250 may be iterated with subsequent images captured by the imaging device 34 to continually provide hitch angle measurements.

[0045] Referring to FIG. 13, a method of locating an imaged hitch point in images captured by the imaging device 34 is illustrated. The method, also referred to herein as “the drawbar scan method,” may be executed by the controller 38 of the trailer backup assist system 10 and may be embodied as a subroutine of the hitch angle detection routine 44. The drawbar scan method generally requires the trailer 12 to be moving relative to the vehicle 14 at a non-zero hitch angle in order to identify an imaged hitch point. As such, the drawbar scan method may be executed to provide a suitable rotation point or projection point when executing the centerline method or the template matching method in instances where the vehicle 14 and trailer 12 are moving along a curved path. By identifying the imaged hitch point, more accurate hitch angle measurements can be achieved.

[0046] The drawbar scan method generally begins at step 300, where the controller 38 selects two images captured by the imaging device 34 that show the trailer 12 at distinct hitch angles. The two images may be successive or non-successive depending on the frame rate of the imaging device 34. In practice, a noticeable difference in hitch angles between the two images is generally preferred. At step 310, the controller 38 derives an edge map for both images by calculating the intensity gradient, or edge value, for each of their corresponding pixels. For purposes of illustration, FIG. 14 shows a first image 312 in which the hitch angle between the vehicle 14 and the trailer 12 is approximately zero whereas FIG. 15 shows a second image 314 in which the hitch angle between the vehicle 14 and the trailer 12 is approximately 5 degrees relative to the zero hitch angle position shown in FIG. 14. For purposes of clarity, the edge maps associated with both images 312, 314 are not shown. At step 320, the controller 38 defines a detection window 322 of variable height and width in both images 312, 314. Each detection window 322 is centered at a common pixel position, such as pixel position 324, which is located on a reference line 326 that extends vertically across the middle column of the corresponding image 312, 314. The reference line 326 is defined by the controller 38 and is assumed to coincide with the center longitudinal axis of an imaged drawbar 327 and intersect with an imaged hitch point 328 between the vehicle 14 and the trailer 12.

[0047] At step 330, the controller 38 determines an average pixel intensity of the pixels bounded by each detection window 322 when centered at the current pixel position, and at step 340, the controller 38 calculates an averaged pixel difference, which is defined herein as the absolute value of the difference between the average pixel intensities, as calculated at step 330. Once the average pixel difference has been calculated, at step 350, the controller 38 shifts each detection window 322 in an upward vertical direction (as specified by arrow 342) so that each detection window 322 is commonly centered at a new pixel position that is 1 or more pixel positions higher on the corresponding reference line 326 than the previous pixel position. Thus, by making multiple iterations of steps 330-350, the controller 38 may calculate averaged pixel differences for when each detection window 322 is commonly centered at a number of pixel positions along the reference line 326. Once this has been done, at step 360, the controller 38 extrapolates the location of the hitch point 328 based on variations in the calculated averaged pixel differences.

[0048] With respect to images 312 and 314, it is generally expected that little variation will occur between the calculated averaged pixel differences associated with pixel positions that coincide with the imaged drawbar 327 due in part to the imaged drawbar 327 appearing in a common fixed position in both images 312, 314. In contrast, it is generally expected that greater variation to occur between the calculated averaged pixel differences associated with pixel positions that are located on portions of the reference line 326 that extend beyond the imaged drawbar 327 due in part to the trailer 12 appearing in different positions in both images 312, 314. For purposes of illustration, a graph is shown in FIG. 16 illustrating calculated averaged pixel differences for a number of pixel positions along the vertical reference line 326. The pixel positions may fall within a predetermined range in which the imaged hitch point 328 is expected to be located, thereby negating the need to determine averaged pixel differences for pixel positions along the vertical reference line 326 that are unlikely to correspond to the imaged hitch point 328.

[0049] As shown in FIG. 16, the graph generally demonstrates a relatively constant averaged pixel difference between 2 and 3 when each detection window 322 is commonly centered at pixel positions 0-44 as those pixel positions coincide with the imaged drawbar 327. In contrast the graph in FIG. 15 generally demonstrates a sharp increase in averaged pixel differences when each detection window 322 is commonly centered at pixel positions 46-70 as those pixel positions are located on portions of the reference line 326 that extend past the imaged drawbar 327. Recognizing this, the controller 38 may select, as the imaged hitch point 328, one of the pixel positions (e.g., pixel position 44 or 45) leading up to the sharp increase in averaged pixel differences. According to one embodiment, the controller 38 may iterate steps 330-350 of the drawbar scan method until the averaged pixel difference meets or exceeds a predetermined threshold value (e.g., 3.5) and select, as the imaged hitch point, the pixel position associated with the calculated averaged pixel difference that meets or exceeds the threshold value. This threshold value may be determined based on a number of considerations including, but not limited to, the size of the detection window 322, properties of the imaging device 34, etc. Once identified, the selected imaged hitch point should closely mirror the actual imaged hitch point 328 and may be used for hitch angle detection pursuant to the template matching method or the centerline method.

[0050] Referring to FIG. 17, a kinematic model of the vehicle 14 and trailer 12 is shown and serves as the basis for determining hitch angle according to another method, referred to herein as “the steady state method” and described in greater detail below. As shown in FIG. 17, the kinematic model is based on various parameters associated with the vehicle 14 and the trailer 12. These parameters include:

[0051] δ: steering angle at steered wheels 60 of the vehicle 14;

[0052] α: yaw angle of the vehicle 14;

[0053] β: yaw angle of the trailer 12;

[0054] γ: hitch angle between the vehicle 14 and the trailer 12 (γ=β−α);

[0055] W: wheelbase length between a front axle 370 and a rear axle 372 of the vehicle 14;

[0056] L: drawbar length between the hitch point 32 and the rear axle 372 of the vehicle 14;

[0057] D: trailer length between the hitch point 32 and axle 20 of the trailer 12 or effective axle for a multiple axle trailer; and

[0058] v: vehicle longitudinal speed.

[0059] From the kinematic model shown in FIG. 17, the yaw rate of the vehicle 14 may be represented with the following equation:

[0060]

\frac{d α}{dt} = - \frac{v}{W} \tan δ

[0061] Furthermore, the yaw rate of the trailer 12 may be represented with the following equation:

[0062]

\frac{d β}{dt} = \frac{v}{D} \sin γ + \frac{Lv}{DW} \cos γ \tan δ

[0063] Accordingly, when the yaw rate of the vehicle 14 and the trailer 12 become equal, the hitch angle γ and the steering angle δ will be constant. This condition, referred to herein as steady state, can occur when a steering command is steadily maintained during a backing maneuver such as when the trailer 12 is reversed in a straight line with the vehicle 14 or when the vehicle 14 and trailer 12 are turning at a constant curvature for at least a threshold period of time or over a threshold distance of motion. Under such steady state driving conditions, the resulting hitch angle γ can be described using the following equation:
c=a cos γ+b sin γ

[0064] This equation can be rewritten as follows:
c=a√{square root over (1−sin²γ)}+b sin γ

[0065] The above equation can be rearranged into quadratic form and rewritten as follows:
c²−a²−2bc sin γ+(b²+a²)sin γ=0

[0066] Solving the quadratic equation for the hitch angle γ yields the following hitch angle equation:

[0067]

γ = \arcsin \frac{bc \pm a \sqrt{b^{2} + a^{2} - c^{2}}}{b^{2} + a^{2}}

Where, c = - \frac{1}{W} \tan δ

b = \frac{1}{D}

a = \frac{L}{DW} \tan δ

[0068] Accordingly, for a particular vehicle and trailer combination, the trailer length D, the wheelbase length W, and the drawbar length L are constant and assumed known. Thus, when the steady state condition is satisfied, the hitch angle γ between the vehicle 14 and trailer 12 may be determined as a function of the trailer length D, the wheelbase length W, the drawbar length L, and the steering angle δ.

[0069] Referring to FIG. 18, the steady state method is shown according to one embodiment. The steady state method may be executed by the controller 38 of the trailer backup assist system 10 and is exemplarily shown as one embodiment of the hitch angle detection routine 44. The method includes determining a steering angle at step 400. The steering angle may be provided by the steering angle sensor 64 and may be compensated to remove any offsets associated therewith. Next, at step 410, a steering angle rate is calculated and is filtered to remove noise. At step 420, it is determined whether the absolute value of the filtered steering angle rate is less than a threshold steering angle rate (e.g., 0.5 degrees per second) required for hitch angle calculation. The method also includes obtaining a hitch angle between the vehicle 14 and trailer 12, as measured pursuant to any of the hitch angle detection methods described herein (e.g., the centerline method) at step 430. At step 440, the controller 38 calculates a filtered hitch angle rate and determines at step 450 whether the absolute value of the filtered hitch angle rate is less than a threshold hitch angle rate (e.g., 0.5 degrees per second) required for hitch angle calculation. The method further includes obtaining a vehicle speed (e.g., from speed sensor 50) at step 460, calculating a filtered vehicle speed at step 470, and then determining at step 480 whether the absolute value of the filtered vehicle speed is greater than a threshold vehicle speed (e.g., 3 kilometers per second) required for hitch angle calculation. If the conditions specified at steps 420, 450, and 480 are met at step 490, the controller 38 determines that the steady state condition has been satisfied and calculates a hitch angle at step 500 using the hitch angle equation described herein with respect to the kinematic model shown in FIG. 17. So long as the steady state condition is satisfied, the controller 38 may continue to determine hitch angle via the hitch angle equation.

[0070] Referring to FIG. 19, a method of initializing hitch angle detection is illustrated. The method, referred to herein as the “hitch angle initialization method,” may be executed by the controller 38 of the trailer backup assist system 10 and is exemplarily shown as one embodiment of the operating routine 46. The hitch angle initialization method includes selecting between the various hitch angle detection methods described previously herein, which include the template matching method, the centerline method, and the steady state method, for the purposes of hitch angle detection. As described in greater detail below, the foregoing hitch angle detection methods generally vary in processing time and reliability. Thus, the hitch angle initialization method is executed in a manner such that the “best available” hitch angle method is chosen based on considerations including the availability of a template image for the trailer 12 being towed and current driving conditions.

[0071] The hitch angle initialization method may begin at step 600, where the controller 38 determines whether a template image is available for the trailer 12 being towed. If so, the controller 38 proceeds to step 610 to determine the hitch angle via the template matching method. The template matching method may determine the hitch angle in approximately 1 second and is generally the most reliable when compared to the centerline method and the steady state method. So long as the template image remains available, the template matching method is selected as the best available hitch angle detection. In the event no template image is available or the template matching method is unable to be executed (e.g., system error), the controller 38 proceeds to step 620 to determine whether the vehicle 14 and trailer 12 are moving in a straight direction. According to one embodiment, the direction of the vehicle 14 and trailer 12 may be determined by obtaining a steering angle from the steering angle sensor 64 over a period of time. If it is determined that the vehicle 14 and trailer 12 are moving in a straight direction, the controller 38 proceeds to step 625 and processes images captured by the imaging device 34 to derive a template image of the trailer 12 before proceeding to step 610 to determine the hitch angle via the template matching method. Otherwise, the controller 38 proceeds to step 630 to determine the hitch angle via the centerline method. The centerline method may determine the hitch angle in less than 1 second but is generally less reliable when compared to the template matching method and the steady state method.

[0072] Once the centerline method is selected, the controller 38 will continue to determine the hitch angle via the centerline method until a steady state condition is satisfied at step 640. As described previously herein, the steady state condition may be satisfied when the vehicle 14 and trailer 12 are moving in a straight direction or moving along a path at constant curvature. Or in other words, the steady state condition is satisfied when the yaw rate of the vehicle 14 and the trailer 12 become equal, thereby resulting in the hitch angle and the steering angle becoming constant. If the steady state condition is satisfied, the controller proceeds to step 650, where it determines whether the hitch angle is substantially zero. In instances where the steady state condition is satisfied due to the vehicle 14 and trailer 12 moving in a straight direction at a constant zero hitch angle value (γ=0), the controller 38 proceeds to step 625 and processes images captured by the imaging device 34 to derive a template image of the trailer 12 before proceeding to step 610 to determine the hitch angle via the template matching method. Otherwise, in instances where the steady state condition is satisfied due to the vehicle 14 and trailer 12 moving along a path at a constant non-zero hitch angle value (λ≠0), the controller proceeds to step 660 to determine the hitch angle via the steady state method. The steady state method may determine the hitch angle in approximately 1-3 seconds and is generally less reliable than the template matching method but more reliable than the centerline method. So long as the steady state condition is satisfied, the controller 38 will select either the template matching method or the steady state method. If the steady state method is the currently selected hitch angle detection method and the steady state condition is no longer satisfied, the controller 38 returns to step 630 to determine the hitch angle via the centerline method.

[0073] It is to be understood that variations and modifications can be made on the aforementioned structures and methods without departing from the concepts of the present invention, and further it is to be understood that such concepts are intended to be covered by the following claims unless these claims by their language expressly state otherwise.

Claims

The invention claimed is:

1. A system for detecting a hitch angle between a vehicle and a trailer, comprising:

an imaging device configured to capture images of the trailer; and

circuitry configured to:

process the captured images;

derive an edge map and identify trailer pixels therein;

define a number of candidate lines projecting from a common projection point in the edge map; and

determine the hitch angle based on an angle between a selected candidate line and a reference line wherein the candidate lines are derived based on a width of a rear vehicle bumper, a drawbar length, and a trailer length; wherein the reference line extends along a middle column of the edge map and intersects an imaged hitch point between the vehicle and the trailer.

2. The system of claim 1, wherein the circuitry processes successive images captured by the imaging device to derive an averaged image and derives the edge map by calculating an edge value for each pixel in the averaged image.

3. The system of claim 2, wherein the circuitry identifies trailer pixels by comparing the edge value of each pixel within the edge map to a threshold value and selecting those pixels exceeding the threshold value to correspond to trailer pixels.

4. The system of claim 1, wherein the projection point corresponds to an imaged hitch point between the vehicle and the trailer.

5. The system of claim 1, wherein the projection point corresponds to a default projection point and is located in the edge map at a position in which an imaged hitch point between the vehicle and the trailer is assumed to be located.

6. The system of claim 1, wherein the reference line is indicative of a predetermined hitch angle.

7. The system of claim 1, wherein the selected candidate line corresponds to whichever candidate line has approximately the same number of trailer pixels on each of its sides.

8. A method of detecting a hitch angle between a vehicle and a trailer, comprising the steps of:

capturing images of the trailer using an imaging device;

providing circuitry for:

processing the captured images;

deriving an edge map and identifying trailer pixels therein;

defining a number of candidate lines in the edge map; and

determining the hitch angle based on an angle between a selected candidate line and a reference line indicating a predetermined hitch angle wherein the candidate lines are derived based on a width of a rear vehicle bumper, a drawbar length, and a trailer length; wherein the reference line extends along a middle column of the edge map and intersects an imaged hitch point between the vehicle and the trailer.

9. The system of claim 8, wherein the circuitry processes successive images captured by the imaging device to derive an averaged image and derives the edge map by calculating an edge value for each pixel in the averaged image.

10. The system of claim 9, wherein the circuitry identifies trailer pixels by comparing the edge value of each pixel within the edge map to a threshold value and selecting those pixels exceeding the threshold value to correspond to trailer pixels.

11. The system of claim 8, wherein the candidate lines project from a common projection point.

12. The system of claim 11, wherein the projection point corresponds to an imaged hitch point between the vehicle and the trailer.

13. The system of claim 11, wherein the projection point corresponds to a default projection point and is located in the edge map at a position in which an imaged hitch point between the vehicle and the trailer is assumed to be located.

14. The system of claim 8, wherein the selected candidate line corresponds to whichever candidate line has approximately the same number of trailer pixels on each of its sides.

Patent Citations (475)

Patent	Date	Inventor	Cited By
US3542390(A)	1970-11-01	Fikes et al.	Applicant
US3605088(A)	1971-09-01	Savelli	Applicant
US3787077(A)	1974-01-01	Sanders	Applicant
US3833928(A)	1974-09-01	Gavit et al.	Applicant
US3860257(A)	1975-01-01	Mesley	Applicant
US4040006(A)	1977-08-01	Kimmel	Applicant
US4042132(A)	1977-08-01	Bohman et al.	Applicant
US4122390(A)	1978-10-01	Kollitz et al.	Applicant
US4212483(A)	1980-07-01	Howard	Applicant
US4366966(A)	1983-01-01	Ratsko et al.	Applicant
US4735432(A)	1988-04-01	Brown	Applicant
US4752080(A)	1988-06-01	Rogers	Applicant
US4848449(A)	1989-07-01	Martinet et al.	Applicant
US4852901(A)	1989-08-01	Beasley et al.	Applicant
US4943080(A)	1990-07-01	Reimer	Applicant
US5001639(A)	1991-03-01	Breen	Applicant
US5056905(A)	1991-10-01	Jensen	Applicant
US5097250(A)	1992-03-01	Hernandez	Applicant
US5108123(A)	1992-04-01	Rubenzik	Applicant
US5108158(A)	1992-04-01	Breen	Applicant
US5132851(A)	1992-07-01	Bomar et al.	Applicant
US5152544(A)	1992-10-01	Dierker, Jr. et al.	Applicant
US5191328(A)	1993-03-01	Nelson	Applicant
US5244226(A)	1993-09-01	Bergh	Applicant
US5246242(A)	1993-09-01	Penzotti	Applicant
US5247442(A)	1993-09-01	Kendall	Applicant
US5282641(A)	1994-02-01	McLaughlin	Applicant
US5289892(A)	1994-03-01	Notsu	Applicant
US5290057(A)	1994-03-01	Pellerito	Applicant
US5455557(A)	1995-10-01	Noll et al.	Applicant
US5517419(A)	1996-05-01	Lanckton	Examiner
US5521633(A)	1996-05-01	Nakajima et al.	Applicant
US5523947(A)	1996-06-01	Breen	Applicant
US5541778(A)	1996-07-01	DeFlorio	Applicant
US5558350(A)	1996-09-01	Kimbrough et al.	Applicant
US5559696(A)	1996-09-01	Borenstein	Applicant
US5579228(A)	1996-11-01	Kimbrough et al.	Applicant
US5631656(A)	1997-05-01	Hartman et al.	Applicant
US5650764(A)	1997-07-01	McCullough	Applicant
US5670935(A)	1997-09-01	Schofield	Examiner
US5690347(A)	1997-11-01	Juergens et al.	Applicant
US5719713(A)	1998-02-01	Brown	Applicant
US5747683(A)	1998-05-01	Gerum et al.	Applicant
US5821852(A)	1998-10-01	Fairchild	Applicant
US5837994(A)	1998-11-01	Stam	Examiner
US5980048(A)	1999-11-01	Rannells, Jr. et al.	Applicant
US6041582(A)	2000-03-01	Tiede et al.	Applicant
US6042196(A)	2000-03-01	Nakamura et al.	Applicant
US6049171(A)	2000-04-01	Stam	Examiner
US6124709(A)	2000-09-01	Allwine	Applicant
US6151175(A)	2000-11-01	Osha	Applicant
US6198992(B1)	2001-03-01	Winslow	Applicant
US6217177(B1)	2001-04-01	Rost	Applicant
US6218828(B1)	2001-04-01	Bates et al.	Applicant
US6223104(B1)	2001-04-01	Kamen et al.	Applicant
US6223114(B1)	2001-04-01	Boros et al.	Applicant
US6268800(B1)	2001-07-01	Howard	Applicant
US6292094(B1)	2001-09-01	Deng et al.	Applicant
US6351698(B1)	2002-02-01	Kubota et al.	Applicant
US6472865(B1)	2002-10-01	Tola et al.	Applicant
US6480104(B1)	2002-11-01	Wall et al.	Applicant
US6483429(B1)	2002-11-01	Yasui et al.	Applicant
US6494476(B2)	2002-12-01	Masters et al.	Applicant
US6498977(B2)	2002-12-01	Wetzel et al.	Applicant
US6539288(B2)	2003-03-01	Ishida et al.	Applicant
US6568093(B2)	2003-05-01	Kogiso et al.	Applicant
US6577952(B2)	2003-06-01	Geier et al.	Applicant
US6587573(B1)	2003-07-01	Stam	Examiner
US6611610(B1)	2003-08-01	Stam	Examiner
US6612394(B2)	2003-09-01	Wessman	Examiner
US6668225(B2)	2003-12-01	Oh et al.	Applicant
US6693524(B1)	2004-02-01	Payne	Examiner
US6704653(B2)	2004-03-01	Kuriya et al.	Applicant
US6712378(B1)	2004-03-01	Austin	Applicant
US6801125(B1)	2004-10-01	McGregor	Examiner
US6806809(B2)	2004-10-01	Lee et al.	Applicant
US6820888(B1)	2004-11-01	Griffin	Applicant
US6838979(B2)	2005-01-01	Deng et al.	Applicant
US6854557(B1)	2005-02-01	Deng et al.	Applicant
US6857494(B2)	2005-02-01	Kobayashi et al.	Applicant
US6879240(B2)	2005-04-01	Kruse	Applicant
US6891563(B2)	2005-05-01	Schofield	Examiner
US6956468(B2)	2005-10-01	Lee	Examiner
US6959970(B2)	2005-11-01	Tseng	Applicant
US6999856(B2)	2006-02-01	Lee et al.	Applicant
US7005974(B2)	2006-02-01	McMahon et al.	Applicant
US7006127(B2)	2006-02-01	Mizusawa et al.	Applicant
US7008088(B2)	2006-03-01	Pisciotti	Applicant
US7028804(B2)	2006-04-01	Eki et al.	Applicant
US7032705(B2)	2006-04-01	Zheng et al.	Applicant
US7046127(B2)	2006-05-01	Boddy	Applicant
US7058493(B2)	2006-06-01	Inagaki	Applicant
US7089101(B2)	2006-08-01	Fischer et al.	Applicant
US7154385(B2)	2006-12-01	Lee et al.	Applicant
US7159890(B2)	2007-01-01	Craig et al.	Applicant
US7167785(B2)	2007-01-01	Lohberg et al.	Applicant
US7170285(B2)	2007-01-01	Spratte	Applicant
US7171330(B2)	2007-01-01	Kruse et al.	Applicant
US7204504(B2)	2007-04-01	Gehring et al.	Applicant
US7219913(B2)	2007-05-01	Atley	Applicant
US7225891(B2)	2007-06-01	Gehring et al.	Applicant
US7229139(B2)	2007-06-01	Lu et al.	Applicant
US7239958(B2)	2007-07-01	Grougan et al.	Applicant
US7269489(B2)	2007-09-01	Deng et al.	Applicant
US7272481(B2)	2007-09-01	Einig et al.	Applicant
US7295907(B2)	2007-11-01	Lu et al.	Applicant
US7401871(B2)	2008-07-01	Lu et al.	Applicant
US7405557(B2)	2008-07-01	Spratte et al.	Applicant
US7413266(B2)	2008-08-01	Lenz et al.	Applicant
US7425889(B2)	2008-09-01	Widmann	Examiner
US7447585(B2)	2008-11-01	Tandy, Jr. et al.	Applicant
US7451020(B2)	2008-11-01	Goetting et al.	Applicant
US7463137(B2)	2008-12-01	Wishart et al.	Applicant
US7504995(B2)	2009-03-01	Lawrence et al.	Applicant
US7532109(B2)	2009-05-01	Takahama et al.	Applicant
US7540523(B2)	2009-06-01	Russell et al.	Applicant
US7548155(B2)	2009-06-01	Schutt et al.	Applicant
US7568716(B2)	2009-08-01	Dietz	Applicant
US7623952(B2)	2009-11-01	Unruh et al.	Applicant
US7648153(B2)	2010-01-01	Metternich et al.	Applicant
US7690737(B2)	2010-04-01	Lu	Examiner
US7715953(B2)	2010-05-01	Shepard	Applicant
US7720580(B2)	2010-05-01	Higgins-Luthman	Examiner
US7731302(B2)	2010-06-01	Tandy, Jr. et al.	Applicant
US7793965(B2)	2010-09-01	Padula	Applicant
US7798263(B2)	2010-09-01	Tandy, Jr. et al.	Applicant
US7878545(B2)	2011-02-01	Rhymer et al.	Applicant
US7881496(B2)	2011-02-01	Camilleri	Examiner
US7904222(B2)	2011-03-01	Lee et al.	Applicant
US7905507(B2)	2011-03-01	Perri	Applicant
US7950751(B2)	2011-05-01	Offerle et al.	Applicant
US7953536(B2)	2011-05-01	Katrak	Applicant
US7974444(B2)	2011-07-01	Hongo	Applicant
US8010252(B2)	2011-08-01	Getman	Examiner
US8010253(B2)	2011-08-01	Lundquist	Applicant
US8036792(B2)	2011-10-01	Dechamp	Applicant
US8038166(B1)	2011-10-01	Piesinger	Examiner
US8044779(B2)	2011-10-01	Hahn et al.	Applicant
US8073594(B2)	2011-12-01	Lee et al.	Applicant
US8157284(B1)	2012-04-01	McGhie et al.	Applicant
US8165770(B2)	2012-04-01	Getman et al.	Applicant
US8167444(B2)	2012-05-01	Lee et al.	Applicant
US8170726(B2)	2012-05-01	Chen et al.	Applicant
US8174576(B2)	2012-05-01	Akatsuka et al.	Applicant
US8180543(B2)	2012-05-01	Futamura et al.	Applicant
US8190364(B2)	2012-05-01	Rekow	Applicant
US8191915(B2)	2012-06-01	Freese, V et al.	Applicant
US8192036(B2)	2012-06-01	Lee et al.	Applicant
US8215436(B2)	2012-07-01	DeGrave et al.	Applicant
US8223204(B2)	2012-07-01	Hahn	Applicant
US8244442(B2)	2012-08-01	Craig et al.	Applicant
US8260518(B2)	2012-09-01	Englert	Examiner
US8267485(B2)	2012-09-01	Barlsen et al.	Applicant
US8280607(B2)	2012-10-01	Gatti et al.	Applicant
US8308182(B2)	2012-11-01	Ortmann et al.	Applicant
US8326504(B2)	2012-12-01	Wu et al.	Applicant
US8342560(B2)	2013-01-01	Albers et al.	Applicant
US8380390(B2)	2013-02-01	Sy et al.	Applicant
US8380416(B2)	2013-02-01	Offerle et al.	Applicant
US8393632(B2)	2013-03-01	Vortmeyer et al.	Applicant
US8401744(B2)	2013-03-01	Chiocco	Applicant
US8427288(B2)	2013-04-01	Schofield et al.	Applicant
US8469125(B2)	2013-06-01	Yu et al.	Applicant
US8504243(B2)	2013-08-01	Kageyama	Applicant
US8548680(B2)	2013-10-01	Ryerson et al.	Applicant
US8548683(B2)	2013-10-01	Cebon et al.	Applicant
US8576115(B2)	2013-11-01	Basten	Applicant
US8626382(B2)	2014-01-01	Obradovich	Applicant
US8675953(B1)	2014-03-01	Elwell et al.	Applicant
US8755984(B2)	2014-06-01	Rupp et al.	Applicant
US8807261(B2)	2014-08-01	Subrt et al.	Applicant
US8825328(B2)	2014-09-01	Rupp et al.	Applicant
US8833789(B2)	2014-09-01	Anderson	Applicant
US8838353(B2)	2014-09-01	Wu	Examiner
US8886400(B2)	2014-11-01	Kossira et al.	Applicant
US8888120(B2)	2014-11-01	Trevino	Applicant
US8909426(B2)	2014-12-01	Rhode	Examiner
US8930140(B2)	2015-01-01	Trombley et al.	Applicant
US8939462(B2)	2015-01-01	Adamczyk et al.	Applicant
US8955865(B2)	2015-02-01	Fortin et al.	Applicant
US8972109(B2)	2015-03-01	Lavoie et al.	Applicant
US9008913(B1)	2015-04-01	Sears et al.	Applicant
US9026311(B1)	2015-05-01	Pieronek et al.	Applicant
US9042603(B2)	2015-05-01	Elwart et al.	Applicant
US9082315(B2)	2015-07-01	Lin et al.	Applicant
US9085261(B2)	2015-07-01	Lu	Examiner
US9102272(B2)	2015-08-01	Trombley	Examiner
US9108598(B2)	2015-08-01	Headley	Applicant
US9114832(B2)	2015-08-01	Wang et al.	Applicant
US9120358(B2)	2015-09-01	Motts et al.	Applicant
US9120359(B2)	2015-09-01	Chiu et al.	Applicant
US9126525(B2)	2015-09-01	Lynam	Examiner
US9156496(B2)	2015-10-01	Greenwood et al.	Applicant
US9164955(B2)	2015-10-01	Lavoie et al.	Applicant
US9180890(B2)	2015-11-01	Lu et al.	Applicant
US9187124(B2)	2015-11-01	Trombley et al.	Applicant
US9227474(B2)	2016-01-01	Liu	Applicant
US9233710(B2)	2016-01-01	Lavoie	Examiner
US9238483(B2)	2016-01-01	Hafner et al.	Applicant
US9248858(B2)	2016-02-01	Lavoie et al.	Applicant
US9264672(B2)	2016-02-01	Lynam	Examiner
US9283892(B2)	2016-03-01	Trombley	Examiner
US9296422(B2)	2016-03-01	Lavoie	Applicant
US9315212(B1)	2016-04-01	Kyrtsos	Examiner
US9321483(B2)	2016-04-01	Headley	Applicant
US9335162(B2)	2016-05-01	Kyrtsos	Examiner
US9340228(B2)	2016-05-01	Xu et al.	Applicant
US9393996(B2)	2016-07-01	Goswami et al.	Applicant
US9428188(B2)	2016-08-01	Schwindt et al.	Applicant
US9434414(B2)	2016-09-01	Lavoie	Applicant
US9446713(B2)	2016-09-01	Lu	Examiner
US9500497(B2)	2016-11-01	Lavoie	Applicant
US9558409(B2)	2017-01-01	Pliefke	Examiner
US9616923(B2)	2017-04-01	Lavoie	Applicant
US9623904(B2)	2017-04-01	Lavoie et al.	Applicant
US9676377(B2)	2017-06-01	Hafner et al.	Applicant
US9827818(B2)	2017-11-01	Hu et al.	Applicant
US2001/0024333(A1)	2001-09-01	Rost	Applicant
US2001/0037164(A1)	2001-11-01	Hecker	Applicant
US2002/0128764(A1)	2002-09-01	Hecker et al.	Applicant
US2003/0133014(A1)	2003-07-01	Mendoza	Examiner
US2003/0137586(A1)	2003-07-01	Lewellen	Examiner
US2003/0234512(A1)	2003-12-01	Holub	Examiner
US2004/0017285(A1)	2004-01-01	Zielinski et al.	Applicant
US2004/0021291(A1)	2004-02-01	Haug et al.	Applicant
US2004/0093139(A1)	2004-05-01	Wildey et al.	Applicant
US2004/0130441(A1)	2004-07-01	Lee	Examiner
US2004/0222881(A1)	2004-11-01	Deng et al.	Applicant
US2005/0000738(A1)	2005-01-01	Gehring	Examiner
US2005/0074143(A1)	2005-04-01	Kawai	Examiner
US2005/0128059(A1)	2005-06-01	Vause	Applicant
US2005/0206224(A1)	2005-09-01	Lu	Applicant
US2005/0206225(A1)	2005-09-01	Offerle	Examiner
US2005/0206229(A1)	2005-09-01	Lu et al.	Applicant
US2005/0206231(A1)	2005-09-01	Lu et al.	Applicant
US2005/0236201(A1)	2005-10-01	Spannheimer et al.	Applicant
US2005/0236894(A1)	2005-10-01	Lu	Examiner
US2005/0236896(A1)	2005-10-01	Offerle	Examiner
US2005/0237385(A1)	2005-10-01	Kosaka	Examiner
US2006/0041358(A1)	2006-02-01	Hara	Applicant
US2006/0050018(A1)	2006-03-01	Hutzel	Examiner
US2006/0071447(A1)	2006-04-01	Gehring et al.	Applicant
US2006/0076828(A1)	2006-04-01	Lu et al.	Applicant
US2006/0103511(A1)	2006-05-01	Lee et al.	Applicant
US2006/0103727(A1)	2006-05-01	Tseng	Examiner
US2006/0111820(A1)	2006-05-01	Goetting et al.	Applicant
US2006/0142936(A1)	2006-06-01	Dix	Applicant
US2006/0152351(A1)	2006-07-01	Daura Luna	Examiner
US2006/0155455(A1)	2006-07-01	Lucas et al.	Applicant
US2006/0244579(A1)	2006-11-01	Raab	Examiner
US2007/0027581(A1)	2007-02-01	Bauer et al.	Applicant
US2007/0090688(A1)	2007-04-01	Haemmerling et al.	Applicant
US2007/0132560(A1)	2007-06-01	Nystrom et al.	Applicant
US2007/0152424(A1)	2007-07-01	Deng et al.	Applicant
US2007/0285808(A1)	2007-12-01	Beale	Applicant
US2008/0143593(A1)	2008-06-01	Graziano et al.	Applicant
US2008/0147277(A1)	2008-06-01	Lu et al.	Applicant
US2008/0231701(A1)	2008-09-01	Greenwood	Examiner
US2008/0312792(A1)	2008-12-01	Dechamp	Applicant
US2009/0005932(A1)	2009-01-01	Lee	Examiner
US2009/0045924(A1)	2009-02-01	Roberts, Sr.	Examiner
US2009/0079828(A1)	2009-03-01	Lee et al.	Applicant
US2009/0085775(A1)	2009-04-01	Otsuka et al.	Applicant
US2009/0093928(A1)	2009-04-01	Getman et al.	Applicant
US2009/0198425(A1)	2009-08-01	Englert	Applicant
US2009/0228182(A1)	2009-09-01	Waldbauer et al.	Applicant
US2009/0248346(A1)	2009-10-01	Fennel et al.	Applicant
US2009/0300701(A1)	2009-12-01	Karaoguz et al.	Applicant
US2009/0306861(A1)	2009-12-01	Schumann et al.	Applicant
US2010/0063702(A1)	2010-03-01	Sabelstrom et al.	Applicant
US2010/0171828(A1)	2010-07-01	Ishii	Applicant
US2010/0332049(A1)	2010-12-01	Sy et al.	Applicant
US2011/0001825(A1)	2011-01-01	Hahn	Applicant
US2011/0018231(A1)	2011-01-01	Collenberg	Applicant
US2011/0022282(A1)	2011-01-01	Wu et al.	Applicant
US2011/0050903(A1)	2011-03-01	Vorobiev	Examiner
US2011/0087398(A1)	2011-04-01	Lu et al.	Applicant
US2011/0112721(A1)	2011-05-01	Wang et al.	Applicant
US2011/0125457(A1)	2011-05-01	Lee et al.	Applicant
US2011/0160956(A1)	2011-06-01	Chung et al.	Applicant
US2011/0257860(A1)	2011-10-01	Getman et al.	Applicant
US2012/0041658(A1)	2012-02-01	Turner	Applicant
US2012/0045112(A1)	2012-02-01	Lundblad	Examiner
US2012/0086808(A1)	2012-04-01	Lynam et al.	Applicant
US2012/0095649(A1)	2012-04-01	Klier et al.	Applicant
US2012/0109471(A1)	2012-05-01	Wu	Applicant
US2012/0112434(A1)	2012-05-01	Albers et al.	Applicant
US2012/0185131(A1)	2012-07-01	Headley	Applicant
US2012/0200706(A1)	2012-08-01	Greenwood	Examiner
US2012/0265416(A1)	2012-10-01	Lu	Examiner
US2012/0271512(A1)	2012-10-01	Rupp et al.	Applicant
US2012/0271514(A1)	2012-10-01	Lavoie et al.	Applicant
US2012/0271515(A1)	2012-10-01	Rhode et al.	Applicant
US2012/0271522(A1)	2012-10-01	Rupp et al.	Applicant
US2012/0283909(A1)	2012-11-01	Dix	Applicant
US2012/0283910(A1)	2012-11-01	Lee et al.	Applicant
US2012/0310594(A1)	2012-12-01	Watanabe	Applicant
US2013/0006472(A1)	2013-01-01	McClain et al.	Applicant
US2013/0024064(A1)	2013-01-01	Shepard	Applicant
US2013/0027195(A1)	2013-01-01	Van Wiemeersch et al.	Applicant
US2013/0082453(A1)	2013-04-01	Padula	Applicant
US2013/0158863(A1)	2013-06-01	Skvarce et al.	Applicant
US2013/0179038(A1)	2013-07-01	Goswami et al.	Applicant
US2013/0207834(A1)	2013-08-01	Mizutani et al.	Applicant
US2013/0226390(A1)	2013-08-01	Luo et al.	Applicant
US2013/0250114(A1)	2013-09-01	Lu	Applicant
US2013/0261843(A1)	2013-10-01	Kossira et al.	Applicant
US2013/0268160(A1)	2013-10-01	Trombley et al.	Applicant
US2014/0005918(A1)	2014-01-01	Qiang	Applicant
US2014/0025260(A1)	2014-01-01	McClure	Applicant
US2014/0052337(A1)	2014-02-01	Lavoie et al.	Applicant
US2014/0058614(A1)	2014-02-01	Trombley et al.	Applicant
US2014/0058622(A1)	2014-02-01	Trombley et al.	Applicant
US2014/0058655(A1)	2014-02-01	Trombley et al.	Applicant
US2014/0058668(A1)	2014-02-01	Trombley et al.	Applicant
US2014/0067154(A1)	2014-03-01	Yu et al.	Applicant
US2014/0067155(A1)	2014-03-01	Yu et al.	Applicant
US2014/0085472(A1)	2014-03-01	Lu et al.	Applicant
US2014/0088824(A1)	2014-03-01	Ishimoto	Applicant
US2014/0160276(A1)	2014-06-01	Pliefke	Examiner
US2014/0172232(A1)	2014-06-01	Rupp et al.	Applicant
US2014/0183841(A1)	2014-07-01	Jones	Applicant
US2014/0188344(A1)	2014-07-01	Lavoie	Applicant
US2014/0188346(A1)	2014-07-01	Lavoie	Applicant
US2014/0200759(A1)	2014-07-01	Lu	Examiner
US2014/0210456(A1)	2014-07-01	Crossman	Applicant
US2014/0218506(A1)	2014-08-01	Trombley	Examiner
US2014/0218522(A1)	2014-08-01	Lavoie et al.	Applicant
US2014/0222288(A1)	2014-08-01	Lavoie et al.	Applicant
US2014/0236532(A1)	2014-08-01	Trombley et al.	Applicant
US2014/0249691(A1)	2014-09-01	Hafner	Examiner
US2014/0267688(A1)	2014-09-01	Aich et al.	Applicant
US2014/0267689(A1)	2014-09-01	Lavoie	Applicant
US2014/0277941(A1)	2014-09-01	Chiu et al.	Applicant
US2014/0277942(A1)	2014-09-01	Kyrtsos	Examiner
US2014/0297128(A1)	2014-10-01	Lavoie et al.	Applicant
US2014/0297129(A1)	2014-10-01	Lavoie et al.	Applicant
US2014/0303847(A1)	2014-10-01	Lavoie	Applicant
US2014/0303849(A1)	2014-10-01	Hafner	Examiner
US2014/0309888(A1)	2014-10-01	Smit et al.	Applicant
US2014/0324295(A1)	2014-10-01	Lavoie	Applicant
US2014/0343795(A1)	2014-11-01	Lavoie	Applicant
US2014/0358429(A1)	2014-12-01	Shutko et al.	Applicant
US2014/0379217(A1)	2014-12-01	Rupp et al.	Applicant
US2015/0002670(A1)	2015-01-01	Bajpai	Examiner
US2015/0035256(A1)	2015-02-01	Klank et al.	Applicant
US2015/0057903(A1)	2015-02-01	Rhode et al.	Applicant
US2015/0066296(A1)	2015-03-01	Trombley et al.	Applicant
US2015/0066298(A1)	2015-03-01	Sharma et al.	Applicant
US2015/0105975(A1)	2015-04-01	Dunn	Applicant
US2015/0115571(A1)	2015-04-01	Zhang et al.	Applicant
US2015/0120141(A1)	2015-04-01	Lavoie et al.	Applicant
US2015/0120143(A1)	2015-04-01	Schlichting	Applicant
US2015/0134183(A1)	2015-05-01	Lavoie et al.	Applicant
US2015/0138340(A1)	2015-05-01	Lavoie	Applicant
US2015/0149040(A1)	2015-05-01	Hueger et al.	Applicant
US2015/0158527(A1)	2015-06-01	Hafner et al.	Applicant
US2015/0165850(A1)	2015-06-01	Chiu et al.	Applicant
US2015/0197278(A1)	2015-07-01	Boos et al.	Applicant
US2015/0203156(A1)	2015-07-01	Hafner et al.	Applicant
US2015/0210254(A1)	2015-07-01	Pieronek et al.	Applicant
US2015/0210317(A1)	2015-07-01	Hafner et al.	Applicant
US2015/0217693(A1)	2015-08-01	Pliefke et al.	Applicant
US2015/0269444(A1)	2015-09-01	Lameyre et al.	Applicant
US2016/0001705(A1)	2016-01-01	Greenwood et al.	Applicant
US2016/0009288(A1)	2016-01-01	Yu	Applicant
US2016/0039456(A1)	2016-02-01	Lavoie et al.	Applicant
US2016/0059780(A1)	2016-03-01	Lavoie	Applicant
US2016/0059888(A1)	2016-03-01	Bradley et al.	Applicant
US2016/0059889(A1)	2016-03-01	Herzog et al.	Applicant
US2016/0096549(A1)	2016-04-01	Herzog et al.	Applicant
US2016/0129939(A1)	2016-05-01	Singh et al.	Applicant
US2016/0152263(A1)	2016-06-01	Singh et al.	Applicant
US2016/0153778(A1)	2016-06-01	Singh et al.	Applicant
US2016/0229452(A1)	2016-08-01	Lavoie et al.	Applicant
US2016/0280267(A1)	2016-09-01	Lavoie et al.	Applicant
US2017/0073005(A1)	2017-03-01	Ghneim et al.	Applicant
US2017/0101130(A1)	2017-04-01	Lavoie	Applicant
US2017/0106796(A1)	2017-04-01	Lavoie et al.	Applicant
CN102582686(B)	2013-09-01		Applicant
DE3923676(A1)	1991-01-01		Applicant
DE3931518(A1)	1991-04-01		Applicant
DE9208595(U1)	1992-08-01		Applicant
DE19526702(A1)	1997-02-01		Applicant
DE10030738(C1)	2001-08-01		Applicant
DE10031244(A1)	2002-01-01		Applicant
DE10065230(A1)	2002-07-01		Applicant
DE10122562(C1)	2002-07-01		Applicant
DE10154612(A1)	2003-05-01		Applicant
DE10312548(B3)	2004-05-01		Applicant
DE10333998(A1)	2005-02-01		Applicant
DE102004050149(A1)	2006-04-01		Applicant
DE102005042957(A1)	2007-03-01		Applicant
DE102005043466(A1)	2007-03-01		Applicant
DE102005043467(A1)	2007-03-01		Applicant
DE102005043468(A1)	2007-03-01		Applicant
DE102006002294(A1)	2007-07-01		Applicant
DE102006048947(A1)	2008-04-01		Applicant
DE102006056408(A1)	2008-06-01		Applicant
DE102008020838(A1)	2008-11-01		Applicant
DE102007029413(A1)	2009-01-01		Applicant
DE102008045436(A1)	2010-03-01		Applicant
DE102006035021(B4)	2010-04-01		Applicant
DE102008043675(A1)	2010-05-01		Applicant
DE102009007990(A1)	2010-08-01		Applicant
DE102009012253(A1)	2010-09-01		Applicant
DE102009027041(A1)	2010-12-01		Applicant
DE102009038552(A1)	2011-02-01		Applicant
DE102010006323(A1)	2011-08-01		Applicant
DE102008004158(B4)	2011-10-01		Applicant
DE102008004159(B4)	2011-10-01		Applicant
DE102008004160(B4)	2011-10-01		Applicant
DE102010021052(A1)	2011-11-01		Applicant
DE102010029184(A1)	2011-11-01		Applicant
DE102010045519(A1)	2012-03-01		Applicant
DE102011104256(A1)	2012-07-01		Applicant
DE102011101990(B3)	2012-10-01		Applicant
DE102012005707(A1)	2012-10-01		Applicant
DE202012010517(U)	2012-12-01		Applicant
DE102011108440(A1)	2013-01-01		Applicant
DE102011120814(A1)	2013-06-01		Applicant
DE102012006206(A1)	2013-10-01		Applicant
DE102012206133(A1)	2013-10-01		Applicant
DE102012019234(A1)	2014-04-01		Applicant
DE102013000198(A1)	2014-07-01		Applicant
EP418653(A1)	1991-03-01		Applicant
EP433858(A2)	1991-06-01		Applicant
EP1361543(A2)	2003-11-01		Applicant
EP1593552(B1)	2007-03-01		Applicant
EP1810913(A1)	2007-07-01		Applicant
EP2388180(A2)	2011-11-01		Applicant
EP2452549(A1)	2012-05-01		Applicant
EP2487454(A2)	2012-08-01		Applicant
EP2551132(A1)	2013-01-01		Applicant
EP2644477(A1)	2013-10-01		Applicant
EP2803944(A2)	2014-11-01		Applicant
FR2515379(A1)	1983-04-01		Applicant
GB2265587(A)	1993-10-01		Applicant
GB2342630(A)	2000-04-01		Applicant
GB2398048(A)	2004-08-01		Applicant
GB2398049(A)	2004-08-01		Applicant
GB2398050(A)	2004-08-01		Applicant
JP61006458	1986-01-01		Applicant
JP6159491(A)	1986-03-01		Applicant
JP6385568(U)	1988-06-01		Applicant
JP1095980(A)	1989-04-01		Applicant
JP1095981(A)	1989-04-01		Applicant
JP9267762(A)	1997-10-01		Applicant
JP9328078(A)	1997-12-01		Applicant
JP10001063(A)	1998-01-01		Applicant
JP11124051(A)	1999-05-01		Applicant
JP11278319(A)	1999-10-01		Applicant
JP2002012172(A)	2002-01-01		Applicant
JP2002068032(A)	2002-03-01		Applicant
JP2003034261(A)	2003-02-01		Applicant
JP2003148938(A)	2003-05-01		Applicant
JP3716722(B2)	2005-11-01		Applicant
JP2008027138(A1)	2008-02-01		Applicant
JP2012105158(A)	2012-05-01		Applicant
JP2012166647(A)	2012-09-01		Applicant
JP2014002056(A)	2014-01-01		Applicant
WO8503263(A1)	1985-08-01		Applicant
WO44605(A1)	2000-08-01		Applicant
WO2005005200(A2)	2005-01-01		Applicant
WO2005116688(A2)	2005-12-01		Applicant
WO2006042665(A1)	2006-04-01		Applicant
WO2012059207(A1)	2012-05-01		Applicant
WO2012103193(A1)	2012-08-01		Applicant
WO2014019730(A1)	2014-02-01		Applicant
WO2014037500(A1)	2014-03-01		Applicant
WO2014070047(A1)	2014-05-01		Applicant
WO2014092611(A1)	2014-06-01		Applicant
WO2014123575(A1)	2014-08-01		Applicant
WO2015074027(A1)	2015-05-01		Applicant
WO2015187467(A1)	2015-12-01		Applicant

Non-Patent Literature (43)

“Ford Super Duty: Truck Technologies”, Brochure, Sep. 2011, 2 pages.Applicant
Kristopher Bunker, “2012 Guide to Towing”, Trailer Life, 2012, 38 pages.Applicant
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.Applicant
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.Applicant
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.Applicant
F.W. Kienhöfer; D. Cebon, “An Investigation of ABS Strategies for Articulated Vehicles”, Cambridge University, Engineering Department, United Kingdom, date unknown, 13 pages.Applicant
C. Lundquist; W. Reinelt; O. Enqvist, “Back Driving Assistant for Passenger Cars with Trailer”, ZF Lenksysteme GmbH, Schwabisch Gmünd, Germany, 2006 (SAE Int'l) Jan. 2006, 8 pages.Applicant
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.Applicant
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.Applicant
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.Applicant
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.Applicant
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.Applicant
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.Applicant
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.Applicant
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.Applicant
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.Applicant
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.Applicant
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.Applicant
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.Applicant
Dieter Zöbel, David Polock, Philipp Wojke, “Steering Assistance for Backing Up Articulated Vehicles”, Systemics, Cybernetics and Informatics; vol. 1, No. 5, date unknown, 6 pages.Applicant
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, date unknown, 11 pages.Applicant
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.Applicant
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.Applicant
Andri Riid, Alar Leibak, Ennu Rüstern, “Fuzzy Backing Control of Truck and Two Trailers”, Tallinn University of Technology; Tallinn, Estonia, date unknown, 6 pages.Applicant
Jane McGrath, “How to Avoid Jackknifing”, A Discovery Company, date unknown, 3 pages.Applicant
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.Applicant
Jujnovich, B.; Roebuck, R.; Odhams, A.; David, C., “Implementation of Active Rear Steering of a Tractor Semitrailer”, Cambridge University, Engineering Department; Cambridge, United Kingdom, date unknown, 10 pages.Applicant
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, date unknown, 13 pages.Applicant
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.Applicant
Stahn, R.; Heiserich, G.; Stopp, A., “Laser Scanner-Based Navigation for Commercial Vehicles”, IEEE, 2007 IEEE Intelligent Vehicles Symposium, Jun. 2007, 1 page.Applicant
Lee Yong H.; Weiwen Deng; Chin Yuen-Kwok Steve; McKay Neil, “Feasibility Study for a Vehicle-Trailer Backing Up Control”, Refdoc.fr, SAE Transactions, vol. 113, No. 6, 2004, 1 page.Applicant
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, vol. 225, No. 7, Jul. 2011, 1 page.Applicant
Haviland, G S, “Automatic Brake Control for Trucks—What Good Is It?”, TRID, Society of Automotive Engineers, Sep. 1968, 1 page.Applicant
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, date unknown, 12 pages.Applicant
“VSE Electronic Trailer Steering”, ETS for Trailers, version 2009, VSE Trailer Systems B.V., 2009, 28 pages.Applicant
“Telematics Past, Present, and Future,” Automotive Service Association, www.ASAshop.org, May 2008, 20 pages.Applicant
“Fully Automatic Trailer Tow Hitch With LIN Bus,” https://webista.bmw.com/webista/show?id=1860575499&lang=engb&print=1, date unknown, 5 pages.Applicant
“VBOX Yaw Rate Sensor With Integral Accelerometers,” Racelogic, www.racelogic.co.uk, date unknown, 2 pages.Applicant
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, vol. 2, No. 3, Sep. 2011, 8 pages.Applicant
Olof Enqvist, “AFS-Assisted Trailer Reversing,” Institutionen för systemteknik Deartment of Electrical Engineering, Jan. 27, 2006, 57 pages.Applicant
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.Applicant
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.Applicant
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.Applicant

Abstract