Method and apparatus for estimating the distance from the trailer axle to the tongue
Patent Information
- Application Number
- DE102014203256
- Authority / Receiving Office
- DE · DE
- Patent Type
- Patents
- Current Assignee / Owner
- Priority Date
- 2013-02-25
- Filing Date
- 2014-02-24
- Publication Date
- 2025-07-24
- Estimated Expiration
- 2034-02-24
Smart Images

Figure 00000000_0000_ABST
Abstract
Description
[0001] The illustrative embodiments generally relate to a method and apparatus for estimating the distance from the trailer axle to the trailer tongue.
[0002] Whether driving, hauling objects, or transporting recreational vehicles, people often hook up trailers to a vehicle's trailer hitch. These trailers come in all shapes and sizes, and they vary in weight and handling capability. Since vehicles now contain computerized systems and modules capable of altering the vehicle's behavior, better control of an otherwise bulky trailer can be achieved if the vehicle knows certain characteristics of the trailer.
[0003] For example, it may be useful for the vehicle to know the trailer length from tongue to axle. Of course, this may require an owner to measure the distance using a tape measure, which isn't easy to find or even own. Furthermore, it may not be clear to the trailer user where to take measurements, which can lead to confusion and inaccurate measurements.
[0004] EP 1 257 799 B1 is known from the prior art. This describes a method for examining the condition of a transport vehicle, wherein the transport vehicle is photographed with one or more linear cameras. A processor is configured to receive an image of the transport vehicle and correct the vehicle or trailer dimensions to the correct dimensions based on known dimensions.
[0005] US 4 778 060 A describes a system for sorting tires, in which an alphanumeric code is located on the tires and read out.
[0006] A system having the features of claim 1 and a method having the features of claim 8 are provided.
[0007] In a first illustrative embodiment, a system includes a processor configured to receive a trailer image. The processor is also configured to identify an axle in the trailer image and to identify a tongue end in the trailer image. Further, the processor is configured to receive a tire image including a wheel diameter provided on a tire. The processor is additionally configured to retrieve the wheel diameter from the tire image. The processor is also configured to identify a wheel in the first image having an identified diameter corresponding to the wheel diameter. Additionally, the processor is configured to calculate a distance from the axle to the tongue end using the identified diameter.
[0008] In a second illustrative embodiment, a computer-implemented method comprises receiving a trailer image. The method also comprises identifying an axle in the trailer image and identifying a tongue end in the trailer image. Further, the method comprises receiving a tire image comprising a wheel diameter provided on a tire. The method additionally comprises retrieving the wheel diameter from the tire image. The method also comprises identifying in the first image a wheel having an identified diameter corresponding to the wheel diameter. Additionally, the method comprises calculating a distance from the axle to the tongue end using the identified diameter.
[0009] In a third illustrative embodiment, a non-transitory computer-readable storage medium stores instructions that, when executed by a processor, cause the processor to perform a method comprising receiving a trailer image. The method also comprises identifying an axle in the trailer image and identifying a tongue end in the trailer image. Further, the method comprises receiving a tire image comprising a wheel diameter provided on a tire. The method additionally comprises retrieving the wheel diameter from the tire image. The method also comprises identifying in the first image a wheel having an identified diameter corresponding to the wheel diameter. Additionally, the method comprises calculating a distance from the axle to the tongue end using the identified diameter. Fig. 1 shows an illustrative vehicle computing system, Fig. 2 shows an illustrative example of an image processing procedure, Fig. 3 shows an illustrative example of an image adjustment procedure, The Fig. 4A and Fig. 4B show illustrative examples of trailer sub-images, and Fig. Figure 5 shows an illustrative example of a display for an attached trailer.
[0010] As required, detailed embodiments of the present invention are disclosed herein; however, it is to be understood that the disclosed embodiments are merely exemplary of the invention and may be embodied in various and alternative forms. The figures are not necessarily to scale; certain features may be exaggerated or minimized to show details of particular components. The specific structural and functional details disclosed herein are therefore not to be interpreted as limiting, but merely as a representative basis for teaching one skilled in the art to variously utilize the present invention.
[0011] Fig. 1 illustrates an exemplary block topology for a vehicle-based computing system 1 (VCS) for a vehicle 31. An example of such a vehicle-based computing system 1 is the SYNC system manufactured by THE FORD MOTOR COMPANY. A vehicle equipped with a vehicle-based computing system may have a front-end visual user interface 4 located within the vehicle. The user may also be able to interact with the user interface, for example, if provided with a touchscreen. In another illustrative embodiment, the interaction occurs through button presses, audible speech, and speech synthesis.
[0012] At the Fig. In the illustrative embodiment 1 shown in FIG. 1, a processor 3 controls at least part of the operation of the vehicle-mounted computing system. The processor, which is provided within the vehicle, allows for the processing of on-board instructions and programs. Furthermore, the processor is connected to both the volatile memory 5 and the non-volatile memory 7. In this illustrative embodiment, the volatile memory is a random access memory (RAM), and the non-volatile memory is a hard disk drive (HDD) or flash memory.
[0013] The processor is also provided with a number of different inputs that allow the user to interface with the processor. In this illustrative embodiment, a microphone 29, an auxiliary input 25 (for input 33), a USB input 23, a GPS input 24, and a BLUETOOTH input 15 are provided. An input selector switch 51 is also provided to allow a user to switch between the various inputs. The input to both the microphone and the auxiliary port is converted from analog to digital by a converter 27 before being passed to the processor. Although not shown, many of the vehicle components and auxiliary components in conjunction with the VCS may utilize a vehicle network (such as, but not limited to, a CAN bus) to transfer data to and from the VCS (or components thereof).
[0014] The system's outputs may include, but are not limited to, a visual display 4 and a speaker 13 or a stereo system output. The speaker is connected to an amplifier 11 and receives its signal from the processor 3 through a digital-to-analog converter 9. The output may also be provided via a remote BLUETOOTH device, such as PND 54, or a USB device, such as a vehicle navigation device 60, along the bidirectional data stream shown at 19 and 21, respectively.
[0015] In one illustrative embodiment, the system 1 uses the BLUETOOTH transceiver 15 to communicate 17 with a user's mobile device 53 (e.g., a mobile phone, smartphone, PDA, or any other device that can be wirelessly connected to a remote network). The mobile device can then be used to communicate 59 with a network 61 external to the vehicle 31, for example, by communicating 55 with a cellular base station 57. In certain embodiments, the cellular base station 57 can be a WiFi access point.
[0016] Example communication between the mobile device and the BLUETOOTH transceiver is represented by signal 14.
[0017] Pairing of a mobile device 53 and the BLUETOOTH transceiver 15 can be instructed by a button 52 or similar input. The CPU is thus instructed to pair the onboard BLUETOOTH transceiver with a BLUETOOTH transceiver in a mobile device.
[0018] Data may be transferred between the CPU 3 and the network 61, for example, using a data service, data over voice, or DTMF tones in conjunction with the mobile device 53. Alternatively, it may be desirable to provide an on-board modem 63 with an antenna 18 to communicate 16 data between the CPU 3 and the network 61 over the voice band. The mobile device 53 may then be used to communicate 59 with a network 61 external to the vehicle 31, for example, by communicating 55 with a cellular base station 57. In certain embodiments, the modem 63 may establish communication 20 with the cellular base station 57 for communicating with the network 61. As a non-limiting example, the modem 63 may be a USB radio modem, and the communication 20 may be radio communication.
[0019] In an exemplary embodiment, the processor is provided with an operating system having a programming interface (API) for communicating with modem application software. The modem application software can access an embedded module or firmware on the BLUETOOTH transceiver to establish wireless communication with a remote BLUETOOTH transceiver (such as that found in a mobile device). Bluetooth is a subset of the IEEE 802 PAN (Personal Area Network) protocols. The IEEE 802 LAN (Local Area Network) protocols include Wi-Fi and have considerable interoperability with IEEE 802 PAN. Both are suitable for wireless communication within a vehicle.Other communication tools that can be used in this area are free-space optical communications (such as IrDA) and non-standard consumer IR protocols.
[0020] In another embodiment, mobile device 53 includes a modem for voiceband or broadband data communication. In the data-over-voice embodiment, a technique known as frequency division multiplexing may be implemented when the owner of the mobile device can speak through the device while data is transferred. At other times, when the owner is not using the device, the data transfer may utilize the entire bandwidth (in one example, 300 Hz to 3.4 kHz). While frequency division multiplexing is common and still in use for analog radio communications between the vehicle and the Internet, it has largely been replaced by hybrid forms using Code Domain Multiple Access (CDMA), Time Domain Multiple Access (TDMA), and Space Domain Multiple Access (SDMA) for digital radio communications.These are all standards compatible with ITU IMT-2000 (3G) and offer data rates of up to 2 mbs for stationary or walking users and 385 kbps for users in a moving vehicle. 3G standards are now being replaced by IMT-Advanced (4G), which offers 100 mbs for users in a vehicle and 1 gbs for the stationary user. If the user has a data service connected to the mobile device, it is possible that the data service allows broadband transmission, and the system could use a much larger bandwidth (which speeds up data transfer). In yet another embodiment, the mobile device 53 is replaced by a radio communication device (not shown) installed on the vehicle 31. In yet another embodiment, the ND 53 may be a wireless local area network (LAN) device capable of communicating, for example (and without limitation), over an 802.11g network (i.e., WiFi) or over a WiMax network.
[0021] In one embodiment, incoming data may pass through the mobile device via a data-over-voice or data service, through the onboard BLUETOOTH transceiver, and into the vehicle's internal processor 3. In the case of certain volatile data, the data may be stored, for example, on the hard drive or other storage medium 7 until the data is no longer needed.
[0022] Additional sources that can interface with the vehicle include a personal navigation device 54, which has, for example, a USB port 56 and / or an antenna 58, a vehicle navigation device 60, which has a USB port 62 or other port, an on-board GPS device 24, or a remote navigation system (not shown) that can connect to the network 61. USB belongs to a class of serial network protocols. The serial protocols IEEE 1394 (Firewire), EIA (Electronics Industry Association), as well as IEEE 1284 (Centronics Port), S / PDIF (Sony / Philips Digital Interconnect Format), and USB-IF (USB Implementers Forum) form the backbone of serial device-to-device standards. Most protocols can be implemented for either electrical or optical communication.
[0023] Furthermore, the CPU could communicate with a variety of other auxiliary devices 65. These devices may be connected via a wireless 67 or wired 69 connection. The auxiliary device 65 may include, but is not limited to, personal media players, wireless health devices, wearable computers, and the like.
[0024] Also, or alternatively, the CPU could be connected to a vehicle-mounted wireless router 73, using, for example, a WiFi transceiver 71. This could allow the CPU to connect to remote networks within the range of the local router 73.
[0025] In addition to example processes being performed by a vehicle computing system located in a vehicle, in certain embodiments, the example processes may be performed by a computing system in communication with a vehicle computing system. Such a system may include, but is not limited to, a wireless device (for example, and without limitation, a cellular phone) or a remote computing system (for example, and without limitation, a server) connected by the wireless device. Collectively, such systems may be called vehicle-associated computing systems (VACS). In certain embodiments, certain components of the VACS may perform particular portions of a process depending on the particular implementation of the system.By way of example and not limitation, if a process includes a step of sending or receiving information with a paired wireless device, the wireless device is likely not performing the process, as the wireless device would not "send and receive" information with itself. One of ordinary skill in the art will understand when it is not appropriate to apply a particular VACS to a given solution. All solutions contemplate that at least the vehicle computing system (VCS) located within the vehicle itself is capable of performing the example processes.
[0026] Although trailer operators may not have access to or knowledge of the proper use of a tape measure or how to input correct measurements into a vehicle, given the prevalence of phones equipped with cameras, it is reasonably likely that the operator has a phone camera available. It is also likely that the operator knows how to use the camera on a phone as a standalone application or combined with an application provided in accordance with the illustrative embodiments.
[0027] By capturing an image of the trailer, an application designed to estimate a distance from the image can be provided with an image usable for the corresponding estimation. Additionally, since a user cannot know a tire size with certainty, an appropriately illuminated image of a tire can provide the application with information that can be used to determine distances within the first image.
[0028] Fig. Figure 2 shows an illustrative example of an image processing approach. In this illustrative embodiment, a vehicle user has been provided with an application for use on a smartphone or other portable device equipped with a camera. This application provides the user with appropriate instructions and access to the required functionality of the device. The processing of the image itself could be performed on a vehicle computing system, although in this example, the process is described as being performed on the portable device.
[0029] Once the application has been launched 201, the user may be prompted to capture an image of the complete trailer, or at least one that includes both the axle and the tongue (i.e., the attachable end) of the trailer. The process receives the complete image 203 once the image has been captured by the user. In this illustrative example, the image processor attempts to identify the distance between a tongue and an axle, as this is useful in providing improved trailer control while the vehicle is moving. The process therefore examines the image to determine whether both a recognizable axle center and a tongue endpoint are present 205.
[0030] Due to poor lighting, poor image quality, rust and discoloration, off-center image acquisition, and other potential problems, the process may not be able to detect an axis and endpoint. In this example, a new image is provided 207 until the correct attributes are present. In other examples, it may not be possible to capture only the image with suitable detectability, and user assistance may be required to identify the attributes. Such user assistance is described in more detail with respect to Fig. 3 discussed.
[0031] Additionally, the process uses the wheel diameter to determine other distances on the image. Since the user may not know the wheel diameter, an image of the tire's exterior can be used to provide the necessary information. In this illustrative example, the process attempts to read the markings on the exterior of tire 209 to determine a wheel diameter.
[0032] If the image is blurry or unreadable (which can often occur due to the distance from which the first image may be taken), the process requests a close-up of the markings on the tire 211. An image is taken and received by the process 213, after which the process determines whether any markings are legible 215. If the markings are unreadable, the process may ask if the user wants to manually enter the wheel diameter 217.
[0033] Since it is possible that the tire's markings have worn or otherwise deteriorated over time, it may be impossible to read the diameter regardless of the number of photographs. In such a case, it may be desirable to manually enter a wheel diameter 221. Otherwise, if the markings are available, a new image more clearly showing the markings can be captured and provided 219 for reading by process 223.
[0034] The process can read the markings (on a legible tire) and determine the wheel diameter 223. Once the diameter is known, the process can examine the original image and determine the distance between two opposite radial locations. The distance (i.e., the diameter) as shown in the image can be used as a scale to measure the distance from the center of the axle to the tongue of the trailer 225, 227. This information can then be passed to a vehicle computing system for later use in controlling the trailer while driving.
[0035] Fig. Figure 3 shows an illustrative example of an image adjustment procedure. In this illustrative example, a user manually identifies the axis center and tab, as may be necessary when the process cannot automatically identify the points. Identification can be provided, for example, by selecting by touching the axis (e.g., at a zoomed location) and also selecting by touching the endpoint of the tab.
[0036] If an image does not have any identifiable points, the process may ask a user if they wish to manually identify the points 301. If manual input is desired, the process may display the first (complete) image for the user 303. From this image, the user may select a tire that can be used for axle identification. The tire selection 305 is then displayed in a zoomed manner 307. If the axle is identifiable, the axle may be selected from the image 309. If the axle and / or the selection is then identifiable from the selection 311, the process may zoom in further.
[0037] Once the axis has been selected, the process zooms out of image 313, and the user selects an area containing tongue 315. The process can zoom back in on tongue 317, and the user can select the "end" of the tongue, which represents the point on the attachable end of the trailer farthest from axis 319. If the end is clearly identifiable once selected 321, the process can display the points on image 323. The user can then confirm that the points accurately represent the correct parts of image 325.
[0038] The Fig. 4A and Fig. 4B show illustrative examples of trailer sub-images. The image shown in Fig. 4A, includes additional identifiers corresponding to user selections or automatically identified points. Tag 401 includes an image of a tire 403 having an axle 409 and a tongue 405.
[0039] In this example, the process identifies a wheel diameter 407 and can visually display the diameter so the user can confirm that the correct identification was applied, meaning they don't want to randomly select the tire diameter or another point. The process can also display a point representing the axle 409 and a label representing the end point of the trailer 411.
[0040] Using the distance represented by the wheel diameter, any other distance between two points in the image can be estimated. The process can therefore estimate the points between the center of the axle and the end of the trailer tongue 413.
[0041] In Fig. 4B shows a close-up of a tire 403. Markings are provided on the side of the tire that can be used to determine the wheel size. In this example, the last two digits of marking 415 identify the wheel size.
[0042] Fig. Figure 5 shows an illustrative example of a display for an attached trailer. This image, which may be displayed on a vehicle display and / or on a mobile device, may show information related to a number of driving characteristics and trailer identifiers. In this example, display 501 includes an image of trailer 505. This may help a user identify a specific trailer if more than one is stored.
[0043] A name / identifier may be provided for the stored trailer 505. The system may also track accumulated miles 507, as well as provide other vehicle-related data, such as gain 509 and current output 511. Other suitable features may also be provided.
[0044] Although exemplary embodiments have been described above, it is not intended that these embodiments describe all possible forms of the invention. The words used in the specification are words of description rather than limitation, and it is to be understood that various changes may be made without departing from the spirit and scope of the invention. In addition, the features of the various embodiments may be combined to form further embodiments of the invention.
Claims
[1] System comprising: a processor (3) configured to receive a trailer image, to identify an axle (409) in the trailer image, to identify a tongue end in the pendant image, receive a tire image having a wheel diameter (407) provided on a tire (403), to get the wheel diameter (407) from the tire image, to identify in the first image a wheel having an identified diameter corresponding to the wheel diameter (407), and to calculate a distance from the axis (409) to the tongue end using the identified diameter. [2] A system according to claim 1, wherein the processor (3) is provided as part of a mobile phone. [3] The system of claim 1, wherein the processor (3) is provided as part of a vehicle computing system. [4] The system of claim 1, wherein the processor (3) is further configured to provide the calculated distance to a trailer control program. [5] The system of claim 1, wherein the identification of the axis (409) and / or the tongue end is assisted by selection by touch by the user. [6] The system of claim 1, wherein the identification of the axle (409), the tongue end and the wheel diameter (407) is automatic. [7] The system of claim 1, wherein the processor (3) is further configured to determine that a wheel diameter (407) cannot be retrieved from the tire image, and to request and receive the input of a wheel diameter (407) if the wheel diameter (407) cannot be retrieved from the tire image. [8] A method comprising a non-transitory computer-readable storage medium storing instructions which, when executed by a processor (3), cause the processor (3) to carry out the method, comprising the following steps: Receiving a trailer image, Identifying an axle (409) in the trailer image, Identifying a tongue end in the tag image, Receiving a tire image having a wheel diameter (407) that is on a Tire (403) is provided, Get the wheel diameter (407) from the tire image, in the first image, identifying a wheel having an identified diameter corresponding to the wheel diameter (407), and Calculating a distance from the axis (409) to the tongue end using the identified diameter. [9] A method according to claim 8, wherein the processor (3) is provided as part of a mobile phone. [10] A method according to claim 8, wherein the processor (3) is provided as part of a vehicle computing system. [11] The method of claim 8, wherein the processor (3) is further configured to provide the calculated distance to a trailer control program. [12] Method according to claim 8, wherein the identification of the axis (409) and / or the tongue end is assisted by selection by touch by the user. [13] The method of claim 8, wherein the identification of the axle (409), the tongue end and the wheel diameter (407) is automatic. [14] The method of claim 8, further comprising: Determining that a wheel diameter (407) cannot be retrieved from the tire image, and Requesting and receiving input of a wheel diameter (407) if the wheel diameter (407) cannot be retrieved from the tire image.
Citation Information
Patent Citations
Method for monitoring transport vehicles
EP1257799B1
Tire processing system
US4778060A