The present disclosure relates to vehicle headlights, and more particularly, to headlight leveling control methods and systems.
Motor vehicles are generally equipped with headlights that are incorporated near the front of a vehicle to assist occupants of the vehicle to see conditions exterior to the vehicle and to allow other vehicles and pedestrians to clearly see the vehicle.
Headlights may be installed to provide particular light projection to surrounding vehicle environments. Headlight intensity and direction are designed to provide an optimal amount of illumination to vehicle surroundings while still ensuring the comfort of other vehicle occupants. Under certain loading conditions, such as increased occupants or hauling or towing cargo, the pitch angle of the vehicle may change resulting in undesirable headlight projection that may lead to poor illumination of surrounding environments and/or discomfort for occupants of nearby vehicles.
Headlight leveling systems have been developed to allow for the angle of light projection to be changed depending on the load conditions of the vehicle. Some systems use a manual control located near a steering wheel, and may be unintuitive to an occupant, hard to use, and require external references to properly select headlight level. Such systems generally utilize a physical switch near the steering controls with several numeric values for each setting, such as 0-5. ‘0’ may represent the setting without adjustment for loading conditions, and ‘5’ may represent the maximum adjusted aim setting in the down direction. When the vehicle is loaded, a user would then be required to reference an external calculation or table to select the correct headlight level setting, or be forced to guess on their own as to which setting is correct.
Automatic headlight leveling systems have been developed that require the use of sensors that determine vehicle conditions, but such systems may be undesirable due to cost and weight.
It will be desirable to provide manual vehicle headlight leveling controls that are easily understood and accessed by occupants of a vehicle that utilize existing vehicle components and systems to reduce the likelihood that the vehicle is operated with undesirable headlight levels.
Systems and methods for vehicle headlight leveling are disclosed that allow for intuitive manual adjustment of headlight levels. Some embodiments may include an input device incorporated into existing vehicle systems and may include graphical or textual representations of vehicle loading conditions. The correct headlight leveling setting may be determined by in-vehicle computing systems based on inputted vehicle loading conditions, and the setting may be automatically outputted to a headlight level control mechanism. The system or method may also prompt an occupant to adjust the headlight level in certain circumstances.
In one embodiment, a headlight leveling system for a vehicle includes an input device adapted to receive an input from an occupant of the vehicle relating to a loading condition of the vehicle, a memory with instructions stored therein, a processor in communication with the input device and the memory, wherein the processor determines a headlight level setting based upon the input and the instructions stored on the memory and outputs a headlight level setting signal, and an adjusting device adapted to change an orientation of a light emitting portion of a vehicle headlight assembly based on the headlight level setting signal.
In another embodiment, a computing device for a vehicle may include one or more processors for controlling operations of the computing device and a memory storing data and instructions used by the one or more processors. The one or more processors may execute instructions stored in the memory to receive an input from an input device in the vehicle corresponding to a vehicle loading condition, determine a headlight level setting based on the input, and output a signal to an adjusting device indicative of the headlight level setting, wherein the adjusting device is adapted to change an orientation of a light emitting portion of a vehicle headlight assembly.
In yet another embodiment, a computer-implemented method for vehicle headlight leveling may include the steps of receiving, by an input device, an input relating to a vehicle loading condition, determining, by a processor in response to instructions stored on a tangible non-transitory computer readable medium and the input, a headlight level setting, and outputting a headlight level setting signal to an adjusting device, the adjusting device adapted to change the orientation of a portion of a headlight assembly of a vehicle.
The various features, advantages, and other uses of the present headlight leveling systems and methods will become more apparent by referring to the following detailed description and drawings in which:
Vehicle headlight leveling methods and systems provide occupants of a vehicle the ability to manually adjust headlight level in an efficient and intuitive manner. In some embodiments, a user may supply a current vehicle loading condition to an input such as a vehicle information or entertainment system. The system may determine a headlight level setting based on the received loading condition using an in-vehicle processor and/or memory. A signal indicative of the headlight level setting may be sent to a headlight leveling device to change the orientation of the vehicle headlight in relation to the body of the vehicle. Some embodiments may prompt a user to input a vehicle loading condition if the vehicle recognizes changed vehicle characteristics.
As used herein, the terminology “headlight” or “headlamp” includes any illumination device attached or incorporated within a vehicle to light surroundings ahead of a vehicle. Headlights may include assemblies adapted to produce both high and low beam settings.
As used herein, the terminology “memory” includes any computer-usable or computer-readable medium or device that can, for example, tangibly contain, store, communicate, or transport any signal or information for use by or in connection with any processor. Examples of computer-readable storage mediums may include one or more read only memories, one or more random access memories, one or more registers, one or more cache memories, one or more semiconductor memory devices, one or more magnetic media, such as internal hard disks and removable disks, one or more magneto-optical media, one or more optical media such as CD-ROM disks, and digital versatile disks (DVDs), or any combination thereof.
As used herein, the terminology “instructions” may include directions for performing any method, or any portion or portions thereof, disclosed herein, and may be realized in hardware, software, or any combination thereof. For example, instructions may be implemented as information stored in the memory, such as a computer program, that may be executed by a processor to perform any of the respective methods, algorithms, aspects, or combinations thereof, as described herein. In some embodiments, instructions, or a portion thereof, may be implemented as a special purpose processor, or circuitry, that may include specialized hardware for carrying out any of the methods, algorithms, aspects, or combinations thereof, as described herein. Portions of the instructions may be distributed across multiple processors on the same machine or different machines or across a network such as a local area network, a wide area network, the Internet, or a combination thereof.
As used herein, the terminology “example”, “embodiment”, “implementation”, “aspect”, “feature”, or “element” indicate serving as an example, instance, or illustration. Unless expressly indicated, any example, embodiment, implementation, aspect, feature, or element is independent of each other example, embodiment, implementation, aspect, feature, or element and may be used in combination with any other example, embodiment, implementation, aspect, feature, or element.
As used herein, the terminology “determine” and “identify”, or any variations thereof, includes selecting, ascertaining, computing, looking up, receiving, determining, establishing, obtaining, or otherwise identifying or determining in any manner whatsoever using one or more of the devices shown and described herein.
As used herein, the terminology “or” is intended to mean an inclusive “or” rather than an exclusive “or”. That is, unless specified otherwise, or clear from context, “X includes A or B” is intended to indicate any of the natural inclusive permutations. That is, if X includes A; X includes B; or X includes both A and B, then “X includes A or B” is satisfied under any of the foregoing instances. In addition, the articles “a” and “an” as used in this application and the appended claims should generally be construed to mean “one or more” unless specified otherwise or clear from context to be directed to a singular form.
Further, for simplicity of explanation, although the figures and descriptions herein may include sequences or series of steps or stages, elements of the methods disclosed herein may occur in various orders or concurrently. Additionally, elements of the methods disclosed herein may occur with other elements not explicitly presented and described herein. Furthermore, not all elements of the methods described herein may be required to implement a method in accordance with this disclosure. Although aspects, features, and elements are described herein in particular combinations, each aspect, feature, or element may be used independently or in various combinations with or without other aspects, features, and elements.
Referring now to
Referring now to
The difference in pitch angle Θ relative to axis 16 may result in undesirable beam 26 as shown in
With reference to
Although depicted as separate units, the processor 110, memory 130, input/output 120, or any combination thereof may be integrated in one or more electronic or computing units. For example, processor 110, input/output device 120, and memory 130 may be integrated within an information and entertainment system located in vehicle 10.
The processor 110 may include any device or combination of devices capable of manipulating or processing a signal or other information now-existing or hereafter developed, including optical processors, quantum processors, molecular processors, or a combination thereof. Processor 110 may, for example, be incorporated with a vehicle electronic control unit (ECU) for in-vehicle information or entertainment systems.
Input/output device 120 may include any device adapted to receive input from an occupant of a vehicle or display information while in communication with processor 110, including now-existing or hereafter developed technology. For example, input/output device 120 may be a touch screen or physical controls located in or on a dashboard or instrument cluster of vehicle 10.
The memory 130 may include any tangible non-transitory computer-usable or computer-readable medium, capable of, for example, containing, storing, communicating, or transporting machine readable instructions, or any information associated therewith, for use by or in connection with the processor 110.
In some embodiments, adjusting device 140 may include one or more motor drivers and motors connected to a portion of a headlight assembly, such as headlight housing, reflector, or brackets. The adjusting device 140 may be adapted to convert electric signals from processor 110 to mechanical movements of at least a portion of headlight assembly 150. For example, adjusting device 140 may cause a portion of headlight assembly 150 containing a light source or reflective lens to be angled with respect to a pivot point located within headlight assembly 150.
Headlight assembly 150 may include any exterior light assembly designed to provide illumination in front of a vehicle. Furthermore, headlight assembly 150 may include a variety of light sources such as tungsten, tungsten-halogen, halogen infrared reflective (HIR), high-intensity discharge (HID), and light-emitting diodes (LED). Headlight assembly 150 may include additional safety features, such as directional or steering headlights, automatic beam switching, adaptive front-lighting systems (AFS), dimming systems, and headlight washing systems.
In some embodiments, an occupant of vehicle 10 may input certain loading conditions to system 100 via input/output device 120. For example, an occupant may select different loading options presented via a display unit located within vehicle 10. System 100 may then determine a correct headlight level setting and adjust the headlights of vehicle 10 accordingly.
In some embodiments, system 100 may also prompt occupants of vehicle 10 to enter loading conditions of vehicle 10 in certain circumstances. For example, if system 100 detects a hauling or towing condition, it may prompt a user to enter load conditions and adjust headlight levels. It is contemplated that system 100 may be configured to prompt occupants of a vehicle to input loading conditions at a variety of different times. For example, system 100 may be configured to prompt occupants during each detected loading change such as going from a normal loading condition to hauling or towing and vice versa.
In some embodiments, system 100 may determine the correct headlight level based on the input received in step 220. For example, processor 110 may determine a level setting based on instructions saved on memory 130 and signals from the input/output device 120 indicative of load conditions selected by the occupant. The instructions saved on memory 130 may include a loading conditions correlation table that correlates loading conditions to leveling settings. The correlation table may include, for example, relationships between different vehicle loading conditions and a headlight leveling setting. The level settings may include discrete values that may correspond to different orientations of headlight assembly 150. Thus, occupants of vehicle 10 would not have to manually look up a correlation table to determine a level setting.
In some embodiments, system 100 may determine whether the correct headlight level is different from a current setting applied to the headlights of vehicle 10 in step 230. If the setting is not different from the current setting, no action need be taken by system 100.
If system 100 determines the correct headlight level setting differs from the current settings, a signal may be sent to adjust headlight orientation in step 240. For example, processor 110 may send a signal to adjusting device 140 indicative of a level setting. Adjusting device 140 may then alter the pitch angle of a portion of headlight assembly 150. For example, adjusting device 140 may pivot or angle a light-emitting portion of headlight assembly 150.
In some embodiments, system 100 may determine, upon detecting of a change in hauling or towing, whether load conditions were received from an occupant of vehicle 10 in step 320. If it is determined that load conditions were not received, system 100 may prompt occupants of vehicle 10 to input loading conditions in step 340. Prompts may include any audial or visual reminder or indication, such as a message displayed on a vehicle display.
If load conditions have been received, system 100 may determine whether the received load conditions reflect the current vehicle loading conditions at step 330. For example, if system 100 detects that vehicle 10 is towing a trailer, it may determine whether or not the load conditions received by an occupant reflect such.
If system 100 determines the received conditions reflect the current loading conditions, no further action may be needed. If the received load conditions do not reflect the current vehicle loading conditions, system 100 may prompt occupants to input loading conditions at step 340.
Referring now to
In some embodiments, occupants may input vehicle loading conditions by selecting graphical representations of the conditions of vehicle 10. For example, display 400 may include text prompt 410 and graphics 420a-c as shown in
As shown in
In some embodiments, a user may input a level setting directly as shown in
In addition to the images of
In some embodiments, system 100 may allow for memory settings for different load conditions. For example, system 100 may receive an input from an occupant of vehicle 10 instructing system 100 to save a particular load condition. System 100 may be adapted to prompt or receive custom naming information correlating to the saved load condition. For example, an occupant may have two trailers that are commonly towed by vehicle 10. System 100 may allow the occupant to save custom load conditions for each trailer and allow the occupant to select the saved custom load conditions rather than the particular load conditions of the vehicle. For example, the loading conditions may be saved in memory 130 and may be selected by an occupant using display 400.
The above-described aspects, examples, and implementations have been described in order to allow easy understanding of the application and are not limiting. On the contrary, the application covers various modifications and equivalent arrangements included within the scope of the appended claims, which scope is to be accorded the broadest interpretation so as to encompass all such modifications and equivalent structure as is permitted under the law.
Number | Name | Date | Kind |
---|---|---|---|
3728538 | Bailly | Apr 1973 | A |
3790771 | Tixier | Feb 1974 | A |
3859516 | Tuzson | Jan 1975 | A |
4013883 | Andres | Mar 1977 | A |
4110819 | Ishikawa | Aug 1978 | A |
4180848 | Schwerin | Dec 1979 | A |
4194235 | Heinlein | Mar 1980 | A |
4733334 | Krey | Mar 1988 | A |
4781465 | Demachi | Nov 1988 | A |
5787370 | Kutscher et al. | Jul 1998 | A |
5907196 | Hayami | May 1999 | A |
5962980 | Kluge | Oct 1999 | A |
6144159 | Lopez | Nov 2000 | A |
6193398 | Okuchi | Feb 2001 | B1 |
6229263 | Izawa | May 2001 | B1 |
6234654 | Okuchi | May 2001 | B1 |
6357898 | Toda | Mar 2002 | B1 |
6445085 | Toda et al. | Sep 2002 | B1 |
6663268 | Toda | Dec 2003 | B1 |
7014345 | Toda | Mar 2006 | B2 |
7054730 | Izawa | May 2006 | B2 |
7104664 | Sugimoto | Sep 2006 | B2 |
7239951 | Sugimoto et al. | Jul 2007 | B2 |
7350944 | Yamazaki | Apr 2008 | B2 |
8602618 | Ahn | Dec 2013 | B2 |
8716935 | Nakazawa | May 2014 | B2 |
20020045978 | Nishimura | Apr 2002 | A1 |
20050047152 | Okumura | Mar 2005 | A1 |
20060267502 | Kubota | Nov 2006 | A1 |
20070268159 | Futamura | Nov 2007 | A1 |
20080247177 | Tanaka | Oct 2008 | A1 |
20090086496 | Todani | Apr 2009 | A1 |
20120272193 | Michaelis | Oct 2012 | A1 |
20130320783 | Huang | Dec 2013 | A1 |
20140301094 | Ehlgen | Oct 2014 | A1 |
Number | Date | Country |
---|---|---|
0497039 | Aug 1992 | EP |
0584942 | Jul 1993 | EP |
0579882 | Jan 1994 | EP |
Entry |
---|
Vehicle Drivers Manual, 4-3. Operating the Lights and Wipers, Undated, in 1 page. |
Toyota, Toyota 2014 Tundra Quick Reference Guide, 2014 (19 pages). |
Toyota, Toyota 2014 Tundra Quick Reference Guide, “Overview”, 2014, pp. 2-5 (2 pages). |
Toyota, 2014 Tundra Owner's Manual, Section 2, “Instrument cluster”, 2014, pp. 93-98 (6 pages). |
Toyota, 2014 Tundra Owner's Manual, Section 4-3, “Operating the lights and wipers”, 2014, p. 190 (1 page). |
Toyota, 2014 Tundra Owner's Manual, Section 5-2, “Setup”, 2014, pp. 256-261 (6 pages). |
Toyota, 2014 Tundra Owner's Manual, Section 9-2, “Customization”, 2014, pp. 530-534 (5 pages). |
Toyota, 2014 Tundra Owner's Manual, 2014 (576 pages). |
Number | Date | Country | |
---|---|---|---|
20160039332 A1 | Feb 2016 | US |