This invention relates to lighting systems for vehicles. More particularly, the invention relates to computer-based control systems that provide for different light configurations of a vehicle such as a security vehicle or a military combat vehicle.
For certain vehicles, such as security or military combat vehicles, it may be desirable to have different lighting configurations using different types of lights. For instance, different lighting configurations may be needed under various battlefield conditions versus standard night time operations. However, certain conventional vehicle mounted lighting fixtures such as in various military combat vehicles employ a fixed lighting configuration with a fixed number of lights and a fixed type of light occupying each light position. If a user desires to replace or swap out a first type of light with a second type of light, such conventional systems would require re-wiring because the combinations, positions and quantity of lights are fixed at the time of installation. In such military vehicles, the lights are hardwired into the vehicle power and switching the operation of the individual lights (or a light bar) is done via a hardwired control panel and individual switches in the cabin of the vehicle. Consequently, replacement of lighting, in such vehicles, requires rewiring to connect a new lighting fixture to a control panel.
Accordingly, there is a need for a vehicle lighting system that provides for lighting configuration and different modes of operation in a convenient manner.
A vehicle lighting control system and method are provided. The vehicle lighting control system includes a light module with light carrier positions for receipt of individual light sources. A lighting controller coupled with the light module is configured to identify a light source type associated with the individual light sources occupying light carrier positions of the light module. A power source coupled with the lighting controller provides power to the individual light sources in accordance with the type of light source identified. The individual light sources are removable from the light module and may be replaced by other light sources of a different type. The lighting controller is adapted to be reconfigured such that the different type of light source associated with the other light sources is identified and power is provided to the other light sources in accordance with the different light source type identified.
The lighting module, for example, may be mounted to a military combat vehicle in which the types of light sources selectively installed, removed, and replaced at the light module may include light emitting diode (LED) lights, infrared (IR) lights, high intensity discharge (HID) lights, or incandescent lights. The power source may be selected from vehicle power, a vehicle battery, or a back-up vehicle battery.
The vehicle lighting control system may include an operator interface that is coupled with the lighting controller in which the operator interface may be configured to program desired modes of operation for the light sources. The lighting controller is configured to associate a mode of operation with the individual light sources and the light sources operate in accordance with the mode of operation assigned. For instance, modes of operation may include light flashing, light intensity, number of lights on, night mode or combat mode of operation. The mode of operation assigned is mapped with the individual light sources and the lighting controller controls the lighting operations for each individual light source in accordance with the mode of operation assignment. The lighting controller is also configured to associate different modes of operation with other light sources. The light sources operate in accordance with their respective mode of operation assigned after replacing removed light sources at the light module. In certain applications, the lighting controller may sequence the application of power applied to individual light sources and send commands to a switching device associated with the light module to control power to the individual light sources.
Power may be provided through power lines installed between the power source, the lighting controller and the switching devices associated with the light modules. Communication signaling may also be provided over communication buses installed between the lighting controller, the switching devices and an operator interface. In some examples, the vehicle lighting control system may have both redundant power distribution and communication paths in which multiple paths of power and communications are provided to the light modules and allow the light modules to remain operational if a power or communication paths is interrupted. The location of the individual light sources may be mapped to addresses on the communication bus or addresses associated with registers in memory for the lighting controller.
The lighting controller receives inputted configuration information relating to the type, quantity and location of the light sources at the light modules. In one example, the configuration information may be mass loaded from a portable data memory device or a computer device, upon system start-up, the lighting controller may initiate diagnostic health tests for the light sources. In some instances, light modules may send health status messages to the lighting controller which determines if the health of individual light sources is satisfactory. The lighting controller may modify (per predefined algorithms stored in memory) power control to the light modules to compensate for any damage assessed.
Referring to
As seen, the vehicle lighting control system 20, in this example, includes one or more vehicle mountable light modules 22 that contain a plurality of removable and replaceable light sources 26. The light sources 26 may be a variety of types of lights and may be configured and reconfigured within the light carrier 24 of a light module 22 as desired without rewiring of the vehicle lighting control system. For example, the vehicle light sources may include LED lights, infrared (IR) lights, high intensity discharge (HID) lights, incandescent lights, or any other type of vehicle light for use in various lighting applications and modes of operation. The lighting controller 36 may include a microprocessor and associated memory for storing configuration software that accommodates reconfiguration of the different types of light sources positioned within the light modules. The light modules 22, in this example, may be designed to apply the highest power load required of the different types of powered light sources (such as large power load requirements of HID lights). The light modules 22 may further be mounted on a military combat vehicle such as a High Mobility Multipurpose Wheeled Vehicle (HMMWV, or “hummvee”), or any other vehicle that may require different lighting applications (e.g., operation modes in which it is desirable that the vehicle remains undetectable). For example, unmanned vehicles that may be controlled remotely during military or security/safety missions may be employed.
In the example system 20 seen in
The operator interface 40 in communication with lighting controller 36 is manipulated by the user/operator to prompt the execution of commands and display output to the user. Operator interface 40, for example, may be positioned at an operator control panel within a cabin of the vehicle and may provide hardware or software based switching to send signal commands over communication bus 38 to the lighting controller 36. The lighting controller 36 in conjunction with power switching devices 28 control operation of the lighting modules 22 and the respective light carrier positions 26 through communication bus 38. As seen in
The vehicle lighting control system 20 may be configured by a user initially installing the number of light modules 22 and the desired types of light sources 26 that will occupy the light carrier positions 24 of the light modules 22. The lighting modules 22 may be mounted directly to the vehicle. Power from the power source 30 and communications may be appropriately set up and wired between the light modules 22, power switch devices 28, lighting controller 36, and operator interface 40. As seen, after the vehicle lighting control system 20 is structurally assembled, the user may initiate the configuration software residing at lighting controller 36. The configuration software identifies the number of light modules 22 and modular light sources 26, and identifies the type of light source occupying each light carrier position 24 of the light modules 22. The configuration software may further provide user programmability through operator interface 40 and allow the user to program desired operation modes of the light sources 26 (e.g., number of light sources simultaneously turned on, flashing lights, light intensities, etc.).
The vehicle lighting control system 20 may be reconfigured without the need to rewire the system. In the vehicle lighting system 20, the user may change the types of light sources 26 occupying the light carrier positions 24 in the light modules as desired. For example, if a military combat vehicle is needed to perform an operation at night, it may be desireable to have all the light sources be IR lights, which would require replacement of all non-IR light sources in the light modules 22 with IR light sources. After all IR light sources have been installed in the lighting system 20, the configuration software is run. The configuration software identifies that all the light sources are IR lights and may prompt the user to program the desired mode of operation for the IR light sources (e.g., all lights on, half of lights on, etc.).
In step 202, lighting controller 36 is placed in configure mode. To place controller 36 in the configure mode, a user at operator interface 40 may select a setup interface screen 500 such as seen in
The logical assignment of light source information to the physical light carrier locations at the light modules 22 proceeds to step 206. In step 206, lighting controller 36 sends a request for identification to the lighting devices (including light modules 22 with light carriers 24, light sources 26, and switching devices 28) on the communication bus 38. In step 208, the lighting devices (e.g., light modules 22 and individual light carrier ports 24) return identification (ID) information to the lighting controller 36. This information includes the type of each individual light source 26 located at the associated physical light carrier ports 24 at each light module 22. Information regarding the type of light source, and the quantity and location of the light sources at each light module is provided. In step 210, the configuration software, or alternatively the user, maps the locations of the light sources 26 installed at set up to the addresses on the communications bus 38. Alternatively, the addresses may be associated with locations or registers in memory for the lighting controller. To configure the light sources 26 at individual light source modules 22, the user may select the “configure modules” option 520 at the setup interface screen 500,
Modes of operation are then assigned to the individual light sources 26 at the light module assemblies 22. In step 212,
In some embodiments, various levels of user access may be granted depending on the type of user. A field service user may, for example, have the ability to use preprogrammed modes of operation. A field service user may be granted further access to run diagnostics and pull logged information from the lighting controller 36 for off-board processing. Field service users, in some instances, may be able to reconfigure lighting and add additional modes of operation. Additionally, set up of pre-programmed modes of operations, running of internal diagnostics and operational tests relating to the manufacturing process may be performed during the manufacturing process. In some embodiments, the lighting controller 36 may also be able to “soft-start” the power demands by individual light sources 26 at light carrier positions 24 and light modules 22 to reduce the power demand associated with turning on all lights at the same time. By doing so, reduction of EMI/EMC power spikes on the vehicle power bus 32 may result and the overall surge capacity for the vehicle lighting control system 20 may be lowered.
If the system meets the health check requirements, then in step 304 the lighting controller 36 informs the user via operator interface 40 that the lighting modules and light sources positioned therein are fit for use. Pre-programmed modes of operation may appear at operator interface 40. In step 306, an operational mode screen may be displayed at operator interface 40. For example, as seen in
In step 308, selection of an operation mode is performed by the user selecting a desired mode from operational mode screen 600,
One example of associating individual light sources with particular operational configurations may involve vehicle light operations for a military combat vehicle. Example operations may include a normal operation mode, an infrared (IR) operation mode, or an HID (high intensity discharge) mode. In a normal operation, use of IR or HID light may be selectively turned on and off when desired. This may be used, in some instances, with vehicles that provide auxiliary lighting for night time service work in which flood lights may be used on the sides or rear of a vehicle. For personal transport vehicles or combat vehicles, light operation in normal mode may be controlled with the lighting controller 36 as an alternative to manual control through a dashboard switch. IR operation may be used with military combat vehicles under low observability circumstances and used on conjunction with users using IR equipment such as IR night vision equipment. In this example of IR operation, the HID lights may be locked out and the IR lights would be activated. HID operation may be used, for example, when military combat vehicles are in transport cross-country and there is minimal or no concern for enemy observability. HID lights could be used in conjunction with vehicle headlights or separately from the headlights.
In other examples, lighting control operations may be performed with unmanned vehicles. The light modules 22 may be mountable to remote-controlled unmanned vehicles with the configuration of lighting modes of operation for the light sources 26 performed remotely from the vehicle. For example, lighting modes of operation may selectively be controlled remotely by a stationary operator when employing remote-controlled unmanned vehicles. Reconfiguration of lighting operations may be performed as military or safety missions dictate. Lighting control may be implemented with the digital communications employed in the control of a remote-controlled unmanned vehicle. With different types of light sources present on a remote-controlled unmanned vehicle, different modes of operation for the light sources may be operated through software programming and communications. Lighting control may also be linked with stimulus-response actions with unmanned vehicles. In particular, the lighting controller 36 may provide power to individual light sources 26 of the remote-controlled unmanned vehicle in response to a stimulus-response action. For example, if the unmanned vehicle were performing perimeter security while using IR vision guidance (in a blackout mode) and the unmanned vehicle encounters a potential threat, the light sources may be controlled to illuminate the threat, alerting personnel of the intruder. Software control over the configuration and lighting operation via the lighting controller provides for advantageous modes of operation in both manned and unmanned vehicles.
In one example embodiment, the lighting controller 36 may initiate a “soft-start” of the light sources 26 by sequencing the application of power applied to the individual light sources 26. Power requirements often differ between the different types of light sources that may be used, such as IR lights, HID lights, incandescent lights, etc. Thus, lighting controller 36 sends commands to the switching devices 28 to control the application of power to the individual light sources 26. By separating the application of power to be applied to different types of light sources 26, this provides for a reduction of electrical current in-rush (and associated EMI/EMC) that occurs when several loads require power at a single instant in time. Managing the power load sequencing for the light sources 26 reduces the peak power needed for the light sources 26 in the system 20. In an alternative arrangement, the “soft start” operation of the light sources 26 may be modified to provide a modulated power signal to the light sources to act as a dimmer control.
During operation, the lighting controller 36 is called upon to monitor the system 20. The lighting controller 36 periodically communicates commands to the light modules 22 and checks the status of individual light sources 26 positioned at light carriers 24 of the light modules 22. Health or operational status information and descriptive information relating to the light sources 26 positioned at light modules 22 are sent from the light modules 22 and received at lighting controller 36.
Damage assessment and control is performed at the vehicle lighting control system 20. In step 312, lighting controller 36 assesses damage that has been done to individual light sources 26 at light modules 22. The lighting controller 36 logs this information into memory for future retrieval. Depending on the level of damage that may have occurred to the vehicle lighting system 20, the lighting controller 36 may send an alert message to the user at operator interface 40 that the system will operate at a degraded mode of operation in step 314. Lighting controller 36 assesses the damage based on the information received and controls the system 20 in a degraded performance mode. In step 316, lighting controller 36 operates in the degraded mode of operation until the damage at issue is addressed or repaired. At the end of an operation cycle, the lighting controller 36 creates post-operational summary information. The controller 36 updates life tables and time to fail information, as well as storing the post-operational summary information in memory for subsequent use and downloading.
In an alternative arrangement, each lighting module assembly 22 may be programmed to send a health status message to the lighting controller 36 at periodic intervals (e.g., every 10 seconds). In this arrangement, the lighting controller 36 may keep a watchdog timer on each light carrier 24 or light source of a lighting module assembly 22 to determine whether it is operational. If the lighting controller 36 fails to receive a status message from a light module 22, the lighting controller 36 initiates additional communication attempts with the light module 22. After a predetermined number of communication attempts and no return messaging, the lighting controller 36 may assume that the lighting module is down and take corrective action in accordance with predefined algorithms stored in memory.
As seen, the vehicle lighting control system provides the ability to pre-configure lighting functions for various operational modes. This may be beneficial for many types of vehicles, such as military combat vehicles. Different types of lighting configurations may be constructed without hard-wiring limitations of conventional systems. When conducting military night operations, the system may, for example, be pre-configured to lock-out the light sources from inadvertent activation in order to prevent visibility of the vehicles from enemy attackers during combat missions. Real-time battle assessment of lighting capabilities and health status information upon system start-up may be achieved. Centralized lighting control for use in manned or un-manned vehicles used in battlefield operations may further be achieved.
The foregoing description of implementations has been presented for purposes of illustration and description. It is not exhaustive and does not limit the claimed inventions to the precise form disclosed. Modifications and variations are possible in light of the above description or may be acquired from practicing the invention. The claims and their equivalents define the scope of the invention. The invention illustratively disclosed herein suitably may be practiced in the absence of any element, part, step, component, or ingredient, which is not specifically disclosed herein.
While in the foregoing detailed description this invention has been described in relation to certain preferred embodiments thereof, and many details have been set forth for purposes of illustration, it will be apparent to those skilled in the art that the invention is susceptible to additional embodiments and that certain of the details described herein can be varied considerably without departing from the basic principles of the invention.
Number | Name | Date | Kind |
---|---|---|---|
5010459 | Taylor et al. | Apr 1991 | A |
5209560 | Taylor et al. | May 1993 | A |
5329431 | Taylor et al. | Jul 1994 | A |
5769527 | Taylor et al. | Jun 1998 | A |
5984494 | Chapman et al. | Nov 1999 | A |
6046550 | Ference et al. | Apr 2000 | A |
6149288 | Huang | Nov 2000 | A |
6252358 | Xydis et al. | Jun 2001 | B1 |
6559777 | Martin et al. | May 2003 | B1 |
6623151 | Pederson | Sep 2003 | B2 |
6774893 | Debiez et al. | Aug 2004 | B2 |
6814459 | Pederson | Nov 2004 | B2 |
6859644 | Wang | Feb 2005 | B2 |
7055994 | Martin | Jun 2006 | B2 |
7064674 | Pederson | Jun 2006 | B2 |
7128450 | Tiesler et al. | Oct 2006 | B2 |
7217020 | Finch | May 2007 | B2 |
7314296 | Machi et al. | Jan 2008 | B2 |
7350945 | Albou et al. | Apr 2008 | B2 |
7434970 | Machi et al. | Oct 2008 | B2 |
7462993 | Sotiriou | Dec 2008 | B2 |
20020043938 | Lys | Apr 2002 | A1 |
20020145394 | Morgan et al. | Oct 2002 | A1 |
20020175641 | Andersen | Nov 2002 | A1 |
20060146553 | Zeng et al. | Jul 2006 | A1 |
20110035404 | Morgan et al. | Feb 2011 | A1 |
Number | Date | Country |
---|---|---|
2230695 | Sep 1990 | JP |
Number | Date | Country | |
---|---|---|---|
20130093324 A1 | Apr 2013 | US |