Vehicle with headlight control
The vehicle system provides user-friendly touchscreen control of adaptive headlights by pivoting or sequencing beam profiles, overcoming geometric challenges in light projection, for enhanced user experience.
Patent Information
- Application Number
- DE102017118535
- Authority / Receiving Office
- DE · DE
- Patent Type
- Patents
- Current Assignee / Owner
- Priority Date
- 2016-08-15
- Filing Date
- 2017-08-14
- Publication Date
- 2024-11-14
- Estimated Expiration
- 2037-08-14
AI Technical Summary
Existing vehicle headlights lack user-friendly control mechanisms, particularly through touchscreen interfaces, and do not account for the geometric complexities of light beam projection due to structural aspects of headlights.
A vehicle system that includes adaptive headlights controlled via a touchscreen, with beam adjustments made by pivoting the headlights or sequencing through predefined beam profiles, and includes calibration tables to map touchscreen pixels to beam profiles, allowing user input to adjust light beams geometrically.
Enables intuitive control of headlights using a touchscreen, addressing geometric complexities and ensuring accurate beam projection, enhancing user experience and functionality.
Smart Images

Figure 00000000_0000_ABST
Abstract
Description
TECHNICAL FIELD
[0001] This disclosure relates to vehicle headlights. GENERAL STATE OF THE ART
[0002] Some vehicles include adaptive headlights (a left adaptive headlight and a right adaptive headlight). The headlights emit light beams (i.e., beam profiles). The adaptive headlights pivot the light beams as the vehicle turns during a turn. A solution is needed to enable user-friendly control of the headlights (and thus the beams) via a touchscreen display. SUMMARY
[0003] A vehicle in accordance with the present disclosure includes: a headlight that produces a beam, a touchscreen, a camera, and one or more processors configured to: (a) display images captured by the camera on the touchscreen; (b) adjust the beam according to touch inputs on the images; (c) deactivate (b) when the vehicle exceeds a predetermined speed; (d) adjust the beam by pivoting the beam from an initial position to a final position. BRIEF DESCRIPTION OF THE DRAWINGS
[0004] For a better understanding of the invention, reference is made to embodiments shown in the following drawings. The components in the drawings are not necessarily to scale, and related elements may be omitted, or in some cases, proportions may be exaggerated to emphasize and clearly illustrate the novel features described herein. Furthermore, system components may be arranged in various ways, as is known in the art. Furthermore, in the drawings, corresponding parts are designated by like reference numerals throughout the different views. Fig. 1 is a block diagram of a vehicle computing system. Fig. 2 is a schematic representation of a vehicle containing the vehicle computing system. Fig. Figure 3 is a schematic representation of the vehicle. Fig. 4 shows different radiation profiles. The Fig. Figures 5 to 10 show a user interface with an image background and various features superimposed over the image. Fig. 11 shows a direction key. Fig. 12 shows a calibration table with a plurality of zones. DETAILED DESCRIPTION OF EXEMPLARY EMBODIMENTS
[0005] Although the invention may be embodied in various forms, some exemplary and non-limiting embodiments are shown in the drawings and described below, it being understood that the present disclosure is to be considered as illustrating the invention by way of example and is not intended to limit the invention to the specific embodiments illustrated.
[0006] In this application, the use of disjunction is intended to include conjunction. The use of definite or indefinite articles is not intended to indicate cardinality. In particular, a reference to "the" object or "an" object is also intended to identify one of a possible plurality of such objects. Furthermore, the conjunction "or" can be used to reflect features that are simultaneously present as one option and mutually exclusive alternatives as another option. In other words, the conjunction "or" should be understood to include "and / or" as one option and "either / or" as another option.
[0007] Fig. 1 shows a computing system 100 of an exemplary vehicle 200. The vehicle 200 is also referred to as a first vehicle 200. The vehicle 200 includes a motor, a battery, at least one wheel driven by the motor, and a steering system configured to rotate the at least one wheel about an axis. Such vehicles are described, for example, in U.S. Patent Application Publication No. US 2017 / 0200369 A1 to Miller et al. ("Miller") and U.S. Patent No. 8,180,547 to Prasad et al. ("Prasad"), both of which are hereby incorporated by reference in their entirety.
[0008] Computing system 100 enables automatic control of mechanical systems within the device. Computing device 100 also enables communication with external devices. Computing system 100 includes a data bus 101, one or more processors 108, volatile memory 107, non-volatile memory 106, user interfaces 105, a telematics unit 104, actuators and motors 103, and local sensors 102.
[0009] The data bus 101 transmits electronic signals or data between the electronic components. The processor 108 performs operations on the electronic signals or data to generate modified electronic signals or data. The volatile memory 107 stores data for immediate retrieval by the processor 108. The non-volatile memory 106 stores data for retrieval to the volatile memory 107 and / or processor 108. The non-volatile memory 106 includes a variety of non-volatile memories, including hard drives, SSDs, DVDs, Blu-rays, etc. The user interface 105 includes displays, touchscreen displays (e.g., touchscreen 105a), keyboards, buttons (e.g., directional control 105b), and other devices that enable user interaction with the computing system. The telematics unit 104 enables both wired and wireless communication with external processors via Bluetooth, cellular data (e.g.,3G, LTE), USB, etc. The telematics unit 104 may be configured to transmit signals at a specific frequency.
[0010] The actuators / motors 103 generate physical results. Examples of actuators / motors include fuel injectors, steering, a motor for transmitting torque to the wheels, windshield wipers, brake light circuits, headlight circuits, transmissions, airbags, haptic motors, or internal combustion engines, etc. The local sensors 102 transmit digital readings or measurements to the processor 108. Examples of suitable sensors include temperature sensors, rotation sensors, seatbelt sensors, speed sensors, cameras, lidar sensors, radar sensors, ultrasonic sensors, infrared sensors, etc. It is understood that the various connected components may be made of Fig. 1 may include separate or dedicated processors and memory. Further details regarding the structure and operations of computing system 100 are described, for example, in Miller and / or Prasad.
[0011] Fig. 2 generally shows and illustrates the vehicle 200 incorporating the computing system 100. Although not shown, the vehicle 200 is in operative wireless communication with a mobile device, such as a cellular phone. Some of the local sensors 102 are mounted on the exterior of the vehicle 200. The local sensor 102a may be an ultrasonic sensor, a lidar sensor, a camera, a video camera, and / or a microphone, etc. The local sensor 102a may be configured to detect objects in front of the vehicle 200, as indicated by the forward sensing area 109a. The local sensor 102b may include one or more ultrasonic sensors, a lidar sensor, an infrared sensor, a camera, a video camera, and / or a microphone, etc. The local sensor 102b may be configured to detect objects behind the vehicle 200, as indicated by the rear sensing area 109b.The left sensor 102c and the right sensor 102d may be configured to perform the same functions for the left and right sides of the vehicle 200. The vehicle 200 includes numerous other sensors 102 located inside the vehicle or on the exterior of the vehicle. These sensors may include any or all of the sensors disclosed by Prasad.
[0012] It is understood that the vehicle 200 is configured to perform the methods and operations described below. In some cases, the vehicle 200 is configured to perform these functions via computer programs stored in the volatile and / or non-volatile memories of the computing system 100. A processor is "configured" to perform a disclosed operation if the processor is in operative communication with a memory storing a software program including code or instructions that implement the disclosed operation. A further description of how the processor, memories, and programs interact is found in Prasad. It is understood that the untethered device and / or an external server in operative communication with the vehicle 200 performs some or all of the methods and operations discussed below.
[0013] According to various embodiments, vehicle 200 includes the features of Prasad's vehicle 100a. According to various embodiments, computing system 100 excludes the features of VCCS 102. Fig. 2 by Prasad. According to various embodiments, the vehicle 200 is in communication with some or all of the Fig. 1 by Prasad, including the untethered device 110, the transmission tower 116, the telecommunications network 118, the Internet 120, and the data processing center 122.
[0014] As used in the claims, the term "loaded vehicle" is hereby defined to mean: "a vehicle including: an engine, a plurality of wheels, a power source, and a steering system; wherein the engine transmits torque to at least one of the plurality of wheels, thereby driving the at least one of the plurality of wheels; wherein the power source provides power to the engine; and wherein the steering system is configured to steer at least one of the plurality of wheels."As used in the claims, the term "equipped electric vehicle" is hereby defined to mean "a vehicle including: a battery, a plurality of wheels, a motor, a steering system; wherein the motor transmits torque to at least one of the plurality of wheels, thereby driving the at least one of the plurality of wheels; wherein the battery is rechargeable and configured to supply electrical energy to the motor, thereby driving the motor; and wherein the steering system is configured to steer at least one of the plurality of wheels."
[0015] As in the Fig. 2 and Fig. 3, the vehicle 200 includes a left headlight 202a and a right headlight 202b. The headlights 202 are adaptive, meaning that the headlights 202 are configured to cast a light beam with a profile based on a steering angle and / or the speed of the vehicle 200 during adaptive steering. According to various embodiments, the headlights 202 comprise the structure of the headlight system 10 described in U.S. Patent No. 8,433,479 to Lukacs et al. ("Lukacs"), which is hereby incorporated by reference in its entirety.
[0016] One of the headlights 202 can Fig. 1 by Lukacs. The other headlight 202 may be a reflection of the Fig. 1 of Lukacs. According to various embodiments, the vehicle 200 is configured to control the headlights 202 via some or all of the functions and operations described in Lukacs, and therefore, the vehicle 200 of the present invention may share some or all of the features of the vehicle described in Lukacs.
[0017] As in Fig. 1 of Lukacs, the headlights 202 of the present invention may include a main light source and a plurality of auxiliary light sources. As shown in Fig. 2 of Lukacs, the vehicle 200 of the present invention can adjust beams of the headlights by activating, deactivating, and / or adjusting the auxiliary light sources. As shown in Fig. 3 of Lukacs, the vehicle 200 of the present invention adjusts the beams during adaptive steering based on a steering angle and vehicle speed (when adaptive steering is enabled).
[0018] Alternatively, or in addition to the auxiliary light sources, the vehicle 200 may be configured to rotate the main light source about (a) a vertical axis (similar to a lighthouse) and (b) a horizontal axis. One or more motors drive the rotation of the main light source. When adaptive steering is enabled, the vehicle controls the motors based on the steering angle and vehicle speed.
[0019] Therefore, it is understood that the vehicle 200 is equipped to adjust the headlamp beams via at least one of two possible configurations: (a) by rotating the headlamps about a vertical axis and a horizontal axis using one or more motors; (b) by activating, deactivating, and / or adjusting the power to a main headlamp and auxiliary headlamps to pivot the beam horizontally and / or vertically.
[0020] The following discussion concerns adjusting the beams of headlights 202 according to user inputs received via a touchscreen 105a and / or the directional keypad 105b. According to various embodiments, beam adjustment according to the method described below is only available when the vehicle is parked. According to various embodiments, user beam adjustment is automatically deactivated when the vehicle is detected as exceeding a certain predetermined speed (e.g., 0 mph or 10 mph).
[0021] When the vehicle adjusts the headlight beams, the beams exiting the headlights pivot from their original position to their new or selected position. As noted above, the new or selected position may be offset horizontally and / or vertically from the original position.
[0022] When the vehicle 200 is equipped with configuration (a), the vehicle 200 commands the one or more motors to (i) rotate the headlight about the vertical axis to a new horizontal position and (ii) rotate the headlight about the horizontal axis (i.e., the axis parallel to the vehicle axes) to a new or selected vertical position. The beam then pivots from an original position to the new user-defined position.
[0023] When the vehicle 200 is equipped with configuration (b), the vehicle 200 can simulate rotation (and thus achieve the panning effect) by sequencing through a series of predetermined beam profiles (with each beam profile being associated with a main headlamp power level and an auxiliary headlamp power level for each of the auxiliary heads).
[0024] For example, the vehicle 200 may achieve a beam profile by (1) activating the main headlight and none of the auxiliary headlights to cast a beam extending generally parallel to the straight road. The vehicle 200 may achieve a beam profile by (2) activating the main headlight and some of the auxiliary headlights to cast a beam extending at a horizontal angle of 5° with respect to the generally straight road and a vertical angle of 5° with respect to the generally straight road. The vehicle 200 may achieve a beam profile by (3) activating the main headlight and all of the auxiliary headlights to cast a beam extending at a horizontal angle of 10° with respect to the generally straight road and a vertical angle of 10° with respect to the generally straight road.By sequencing through profiles (1), (2), and (3), the selected spotlight pivots from profile (1) to profile (3). It is understood that both spotlights can pivot simultaneously, and one spotlight can pivot independently of the other.
[0025] Fig. 4 generally shows and illustrates three beam profiles. The vehicle 200 alternates between a first beam profile 401, a second beam profile 402, and a third beam profile 403. The first beam profile 401 may be beam profile (1), the second beam profile 402 may be beam profile (2), and the third beam profile 403 may be beam profile (3). The first beam profile 401 is parallel to the road. The second beam profile 402 has a horizontal angle X and a perpendicular angle Y with respect to the road. The third beam profile 403 has a horizontal angle 2*X and a perpendicular angle 2*Y with respect to the road.
[0026] When the vehicle 200 is equipped with configuration (b), the vehicle 200 simulates headlight rotation (i.e., provides the swivel action) by sequencing through the beam profiles according to the following order: [Beam Profile (1), Beam Profile (2), Beam Profile (3)], assuming that Beam Profile (1) corresponds to the initial position and Beam Profile (3) corresponds to the user-defined final position. With additional beam profiles (e.g., 20 beam profiles), the vehicle 200 can create a more authentic rotation simulation.
[0027] With reference to the Fig. 5 to 10, the vehicle 200 includes a touchscreen display 105a mounted on an instrument panel of the vehicle. The vehicle 200 is configured to display a very recent image captured by the leading local sensor 102a in the display 105a. If the leading local sensor 102a is a video camera, the image updates at a predetermined frequency (e.g., 24 times per second). Although the leading local sensor 102a in Fig. 3 as being mounted on the windshield, the leading local sensor 102a may be located at any suitable location (e.g., mounted just above a front bumper of the vehicle 200).
[0028] In the Fig. 5 to 10, the leading local sensor 102a (e.g., the video camera) has captured the ground or road surface 502, an object 504 (e.g., a box), the horizon 501, and the sky 503. The image displayed in the display 105a shows the current view from the leading local sensor 102a. If the view changes (e.g., a vehicle drives over the ground or road surface 502), the image shown in the display 105a is updated accordingly. In other words, the displayed image is a single frame of a video consisting of a plurality of frames per second.
[0029] As in Fig. 5, the present invention allows the user to place an icon 505 on the image. The user can place the icon 505 by touching or pressing the touchscreen display 105a. In response, one or both spotlights 201, 202 pivot from their current position to point at the location 505. Referring to Fig. 6, the left beam 201a of the left headlight 202a and the right beam 201b of the right headlight 202b now point at the symbol 505. In particular, and as explained further below, the headlights “point” by casting a beam associated with a zone that encloses or bounds the symbol 505 in the two-dimensional space of the touchscreen 105a.
[0030] Controlling headlight beams presents two problems: First, beam profiles are complicated and do not take simple geometric relationships into account due to inherent structural aspects of the headlights (e.g., the shape of the headlight cones). See, for example, Fig. 3 through 7 of U.S. Patent Publication No. 2004 / 0114379 to Miller et al. ("Miller-2"), which is hereby incorporated by reference in its entirety. Furthermore, light rays are three-dimensional, while displays, such as touchscreen display 105a, are two-dimensional.
[0031] To address these problems, the headlights 202 may be calibrated during manufacture. Each calibration may be represented as a calibration chart divided into a plurality of zones, as shown in Fig. 9. Each calibration chart (i.e., both the left headlight calibration chart and the right headlight calibration chart) assigns each pixel of touchscreen 105a to a zone. Each zone maps (a) a beam profile or (b) no beam profile (i.e., a dead zone, as explained in more detail below).
[0032] Fig. Figure 9 shows a calibration chart for the left headlight. The vehicle includes a similar, but mirrored or inverted, chart for the right headlight 202b. The calibration chart of Fig. 9 divides the image shown in the touchscreen display 105a into a plurality of zones 911 to 919 using the vertical dividing lines 901 and 901b and the horizontal dividing lines 902a and 902b. Each of the zones 911 to 919 corresponds to (a) a preset left beam profile 202a or (b) a dead zone. Each zone 911 encloses at least one pixel of the image and, in preferred embodiments, a plurality of pixels. Although the calibration chart of Fig. 9 as occupying the entire touchscreen display 105, it should be understood that the calibration chart is only overlaid on the image of the environment the vehicle is traveling on. Therefore, if the image occupies less than the entire touchscreen (e.g., the upper right corner), the calibration chart is resized to overlay only the portion of the touchscreen showing the image.
[0033] When equipped with configuration (a), the vehicle can adjust the motors to adjust the beam according to the preset horizontal and vertical angle of the headlamp assigned to the zone at the time of manufacture. When equipped with configuration (b), the vehicle will activate the main headlamp and the selected auxiliary lamps according to the beam assigned to the selected zone. In sum, and as noted above, each of zones 911 to 919 maps (a) a different beam or (b) a dead zone (i.e., no beam profile).
[0034] In practice, the segmentation of the zones can be finer than in Fig. 9. In particular, instead of nine separate zones, the vehicle may include hundreds or thousands of separate zones. Fig. 12, for example (explained further below), shows the touchscreen 105a segmented into 16 zones.
[0035] According to various embodiments, and as in Fig. As shown in Figure 7, the user has designated a left headlight icon 505a and a separate right headlight icon 505b to illuminate different locations. Touchscreen 105a displays a switch (not shown) that allows the user to select either the left headlight mode, the right headlight mode, or the both headlight mode (i.e., dual mode).
[0036] After the user operates the switch, the user touches the screen to adjust the one or more headlights associated with the selected switch. The vehicle 200 adjusts the selected headlight(s) according to the calibration chart(s) associated with the selected headlight(s). Fig. 9. In particular, the vehicle 200 adjusts the left headlight 202a according to the left calibration chart and the right headlight 202b according to the right calibration chart.
[0037] As stated above, the vehicle 200 sweeps the beams from their original position to their final or selected position. Thus, when the vehicle 200 is equipped with configuration (b), the vehicle sequences through a series of beams that includes the original beam, one or more intermediate beams, and the final beam. The intermediate beams may correspond to zones located on a path between the original position and the final position. For example, with reference to Fig. 9. If the left headlight was originally pointing at zone 911 and the user touched a pixel within zone 919, the left headlight will sequence through the following series of rays [zone 911, zone 915, and zone 919]. To find the intermediate profiles, the vehicle can draw a line or determine a line from a central location (e.g., a center point) of the original zone to the central location (e.g., the center point) of the final or selected zone, and then sequence through each zone (and thus the headlight profiles associated with the zones) divided by the line.
[0038] When equipped with configuration (b), the vehicle 200 projects the beam associated with each zone of the array for a predetermined duration. According to some embodiments, the vehicle 200 applies a zone for a duration proportional to the length of the segment enclosed in the zone. Fig. Figure 12 shows the image segmented into sixteen square zones. The center of zone 1201 is center point 1201a. The center of zone 1215 is center point 1215a. The element symbols are not superimposed on the image.
[0039] With reference to Fig. 12, one of the headlights (e.g., left headlight 202a) originally cast a beam associated with zone 1201. Then, the user placed a left headlight symbol 505a on display 105a corresponding to zone 1215. In response, left headlight beam 201a sweeps from zone 1201 to zone 1215 according to segment 1216 connecting center point 1201a of zone 1201 to center point 1215a of zone 1215.
[0040] Segment 1216 has a first length 1216 enclosed in zone 1201, a second length 1216b enclosed in zone 1205, a third length 1216c enclosed in zone 1206, a fourth length 1216d enclosed in zone 1210, a fifth length 1216e enclosed in zone 1211, and a sixth length 1216f enclosed in zone 1215. Therefore, the vehicle sequences through the following series: [the beam calibrated at zone 1201 for a duration proportional to length 1216a; the beam calibrated at zone 1205 for a duration proportional to length 1216b; the beam calibrated at zone 1206 for a duration proportional to length 1216c; etc.]. Since zone 1215 is the selected or final zone, the vehicle assigns an unlimited time to zone 1215 (ie, applies the beam calibrated to zone 1215 without reference to longitude 1216f).According to various embodiments, the vehicle immediately jumps from the original zone to the second zone (e.g., assigns a time of zero to zone 1201).
[0041] When the vehicle is equipped according to configuration (a), the vehicle plots a first point on a two-dimensional diagram with an x-coordinate equal to the horizontal angle of the original zone and a y-coordinate equal to the vertical angle of the original zone. The vehicle plots a second point on the two-dimensional diagram with an x-coordinate equal to the horizontal angle of the final or selected zone and a y-coordinate equal to the vertical angle of the final or selected zone. The vehicle then commands the one or more motors to sweep the headlight along a segment connecting the first point to the second point at a constant speed. The motors may be stepper motors, and therefore the headlight may temporarily stop while following the segment.
[0042] Due to technical constraints (e.g., constraints caused by the geometry of the headlights), the vehicle 200 may not be able to move the headlights to any position displayed on the touchscreen 105a. Fig. 8 shows the boundary 801a of the left headlight and a boundary 801b of the right headlight superimposed on the touchscreen 105a. The boundaries divide the image displayed on the touchscreen 105a into the areas 802 to 805.
[0043] The left headlight 202a is capable of being adjusted to point to locations within areas 802 and 805. The left headlight 202a is not capable of being adjusted to point to locations within areas 803 and 804. Areas 803 and 804 are therefore blind areas for the left headlight 202a. The right headlight 202b is capable of being adjusted to point to locations within areas 804 and 805. The right headlight 202b is not capable of being adjusted to point to locations within areas 802 and 803. Areas 802 and 803 are therefore blind areas for the right headlight 202b. It is therefore understood that area 803 is a blind area for both the left headlight 202a and the right headlight 202b.
[0044] As previously stated, the vehicle may overlay boundaries 801 and / or the regions 802 to 805 over the image to guide the user. The boundaries 801 and the regions 802 to 805 may be stored in the vehicle 200 during manufacture. Although the boundaries 801 are shown linearly, in practice they may resemble steps that follow the perimeter of the calibration zones. For example, the right boundary 801b may be described with reference to Fig. 12 follow the following segments: (a) the segment between zones 1214 and 1215, (b) the segment between zones 1210 and 1214, (c) the segment between zones 1209 and 1210, and (d) the segment between zones 1205 and 1209. Consequently, zones 1209, 1213 and 1214 correspond to area 802.
[0045] With reference to Fig. 8, one or both boundaries 801a and 801b may appear and / or disappear automatically, depending on which headlight has been selected with the switch. For example, with reference to Fig. 7, if a user switches to controlling only the left headlight 202a with the left headlight icon 505a, then only the boundaries and / or areas relevant to the left headlight are displayed. For example, the left headlight boundary 801a is displayed and the right headlight boundary 801b is not displayed. Areas 803 and 804 can be grayed or dimmed. If the right headlight 202b is already on and projecting a beam corresponding to a specified zone, the right headlight 202b maintains the beam while the left headlight 202a is operated.
[0046] With reference to Fig. 9 and Fig. 12 it is understood that the calibration table, similar to the limits 801, can be placed over the image. Fig. Figure 9 shows the calibration chart that divides the image displayed on the touchscreen 105a into zones. The boundaries 801 can be displayed (e.g., as steps), and the dead zones can be grayed out. The charts for the left headlight and the right headlight can be configured according to the same geometry (e.g., as shown in Fig. 9 or Fig. 12) over the image, but the right headlight zones would be connected with reversed or mirrored operations compared to the left headlight zones.
[0047] As previously stated, the user can touch a pixel of the image. In response, the vehicle 200 adjusts or pivots the selected headlight(s) in the selected direction. Alternatively, the user can, as in Fig. 10, drag an icon along the image, creating a manual pan that follows the dragged path.
[0048] In Fig. 10, the user switched to dual mode and placed a dual symbol 505 at D1. The user then dragged the dual symbol 505 along path 1001a to D2. After D2, the user dragged the dual symbol 505 along path 1001b and path 1001c to R3. Note that R3 lies within area 804, which is a blind area for the left headlight 202a. Therefore, the vehicle automatically removes the "D" that automatically displays above the dual symbol 505 and automatically displays an "R" above the right symbol 505b. The "R" indicates that only the right headlight is illuminated, corresponding to symbol 505b. Instead of the letters "D," "R," and "L," the vehicle can simply change the color or geometry of the symbol. For example, green symbols may correspond to dual mode; red symbols may correspond to left mode; and blue symbols may correspond to right mode.
[0049] If the user drags the symbol 505 along the path 1001b, the symbol 505 reaches the left headlight boundary 801a at point 1002. At point 1002, the left headlight 202a switches off and the symbol 505 with the "D" changes to the symbol 505b with the "R".
[0050] Fig.11 generally shows and illustrates a directional keypad 105b. The directional key 105b enables the user to adjust one or both headlights (depending on what has been selected with the switch) using the directional keys 1101 through 1104. Instead of pressing the image via the touchscreen 105a, the user can press the directional key 105b to operate the selected headlight(s). According to various embodiments, clicking a directional key (e.g., up key 1101) causes the headlight(s) to transition to an adjacent zone (e.g., the up key 1101 causes the selected headlight(s) to move up one zone). The directional key 105b may be displayed on the touchscreen 105a or may be a separate physical key, for example, located on the instrument panel or steering wheel. If the direction key 105b is displayed on the touchscreen 105a, the direction key 105b is virtual.If the virtual directional button 105b is placed over the image, the virtual directional button 105b can be transparent and movable by the user.
[0051] Although the invention has been applied to headlights, as previously explained, it should be understood that the invention can be applied to other light sources, such as a vehicle's taillights (or any other light source). Vehicles typically include at least two types of taillights: brake lights, which illuminate when the vehicle brakes, and taillights, which illuminate simultaneously with the headlights (i.e., the taillights are intended to always be on when the vehicle is traveling in the dark).
Claims
[1] Vehicle comprising: a headlight configured to produce a beam; a camera configured to capture images in front of the vehicle; a touchscreen configured to display the images; and one (or more) processor(s) configured to: (a) Displaying the images captured by the camera on the touchscreen; (b) controlling the spotlight to move the beam according to touch inputs on the images; and (c) Deactivate (b) when the vehicle exceeds a specified speed. [2] The vehicle of claim 1, wherein the processor(s) is (are) configured to: to adjust the beam by pivoting the beam from an original position to a final position. [3] The vehicle of claim 2, wherein the headlamp includes a main headlamp and a plurality of auxiliary heads, and the processor(s) is (are) configured to sweep the beam from the initial position to the final position by sequencing through a series of beams, each beam of the series of beams being associated with a power level for the main headlamp and each of the plurality of auxiliary heads. [4] The vehicle of claim 1, wherein the processor(s) is (are) configured to: to adjust the beam according to a calibration chart. [5] The vehicle of claim 4, wherein the calibration panel divides the images into a plurality of zones. [6] A vehicle according to claim 5, wherein a plurality of the zones are each associated with a single beam and wherein a plurality of the zones are each associated with no beam. [7] The vehicle of claim 6, wherein the processor(s) is (are) configured to: to control the headlight to produce the individual beams, each beam being associated with either (a) a power level(s) for the headlight or (b) an angle of the headlight. [8] The vehicle of claim 1, wherein the processor(s) is (are) configured to: adjust the beam by sequencing the headlight through a plurality of beams, including an initial beam, intermediate beams, and a final beam. [9] A vehicle according to claim 8, wherein each of the initial beam, intermediate beams and final beam is associated with a different power level for the headlamp. [10] The vehicle of claim 8, wherein the processor(s) is (are) configured to: the beam according to a calibration table which divides the images into a plurality of zones including a first zone, second zones and a third zone. [11] A vehicle according to claim 10, wherein the initial beam is associated with the first zone, the intermediate beams are associated with the second zones, and the final beam is associated with the third zone. [12] The vehicle of claim 11, wherein the processor(s) is (are) configured to: to determine a segment extending from the first zone to the third zone. [13] The vehicle of claim 12, wherein the processor(s) is (are) configured to: To determine zones between the first zone and the third zone which are shared by the extending segment and to set the determined zones as the second zones. [14] The vehicle of claim 13, wherein the processor(s) is (are) configured to: for each of the second zones, to apply the second zone for a time based on a length of the segment dividing the second zone. [15] The vehicle of claim 1, wherein the headlight is a first headlight producing a first beam, and the vehicle includes a second headlight producing a second beam; where the processor(s) is (are) configured to: to allow the first and second beams to be adjusted independently. [16] The vehicle of claim 15, wherein the processor(s) is (are) configured to: Overlay boundaries consistently to determine dead spots of the headlights across the images. [17] The vehicle of claim 16, wherein the processor(s) is (are) configured to: to allow the user to overlay the following on the images: (a) a first symbol corresponding to a mode with only the first headlight; (b) a second symbol corresponding to a mode with only the second headlight; (c) a third symbol corresponding to a dual headlight mode. [18] The vehicle of claim 17, wherein the processor(s) is (are) configured to: in response to a user placing the third icon in one of the known dead zones, the third icon will automatically switch to either the first icon or the second icon. [19] A vehicle according to claim 1, including a directional keypad; where the processor(s) is (are) configured to: to adjust the beam according to the inputs on the directional keyboard. [20] A method of operating a vehicle, comprising: (a) taking pictures in front of the vehicle, using at least one camera; (b) displaying the images captured by the at least one camera on a touchscreen; (c) controlling the spotlight to move a beam generated by the spotlight in accordance with touch inputs on the images; and (d) Deactivate (c) when the vehicle exceeds a specified speed.
Citation Information
Patent Citations
Vehicle headlight system
US20040114379A1
System and method for coordinating v2x and standard vehicles
US20170200369A1
Telematics system and method for traction reporting and control in a vehicle
US8180547B2
Adaptive front-lighting system with fuzzy logic control
US8433479B2
