US8089350B2 - Vehicle light system - Google Patents
Vehicle light system Download PDFInfo
- Publication number
- US8089350B2 US8089350B2 US12/614,866 US61486609A US8089350B2 US 8089350 B2 US8089350 B2 US 8089350B2 US 61486609 A US61486609 A US 61486609A US 8089350 B2 US8089350 B2 US 8089350B2
- Authority
- US
- United States
- Prior art keywords
- current
- vehicle
- input
- over
- outputs
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Expired - Fee Related, expires
Links
- 238000005286 illumination Methods 0.000 claims abstract description 83
- 238000000034 method Methods 0.000 claims description 125
- 230000004913 activation Effects 0.000 claims description 15
- 230000004044 response Effects 0.000 claims description 15
- 238000012544 monitoring process Methods 0.000 claims description 9
- 238000004891 communication Methods 0.000 claims description 7
- 230000003213 activating effect Effects 0.000 claims description 4
- 230000011664 signaling Effects 0.000 claims 7
- 238000012795 verification Methods 0.000 claims 3
- 230000007423 decrease Effects 0.000 claims 2
- 230000003247 decreasing effect Effects 0.000 claims 2
- 238000010586 diagram Methods 0.000 description 6
- 238000012545 processing Methods 0.000 description 6
- 230000002411 adverse Effects 0.000 description 3
- 230000000712 assembly Effects 0.000 description 3
- 238000000429 assembly Methods 0.000 description 3
- 230000009849 deactivation Effects 0.000 description 3
- 230000009977 dual effect Effects 0.000 description 3
- 230000000694 effects Effects 0.000 description 3
- 239000007787 solid Substances 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 2
- 230000008569 process Effects 0.000 description 2
- 230000004075 alteration Effects 0.000 description 1
- 229910052782 aluminium Inorganic materials 0.000 description 1
- XAGFODPZIPBFFR-UHFFFAOYSA-N aluminium Chemical compound [Al] XAGFODPZIPBFFR-UHFFFAOYSA-N 0.000 description 1
- 238000003491 array Methods 0.000 description 1
- 230000008901 benefit Effects 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 238000001514 detection method Methods 0.000 description 1
- 239000013536 elastomeric material Substances 0.000 description 1
- 230000002708 enhancing effect Effects 0.000 description 1
- 230000005669 field effect Effects 0.000 description 1
- 238000010438 heat treatment Methods 0.000 description 1
- 230000000977 initiatory effect Effects 0.000 description 1
- 239000003550 marker Substances 0.000 description 1
- 229910052751 metal Inorganic materials 0.000 description 1
- 239000002184 metal Substances 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012913 prioritisation Methods 0.000 description 1
- 208000011726 slow pulse Diseases 0.000 description 1
- 230000009897 systematic effect Effects 0.000 description 1
- 230000001052 transient effect Effects 0.000 description 1
Images
Classifications
-
- B—PERFORMING OPERATIONS; TRANSPORTING
- B60—VEHICLES IN GENERAL
- B60Q—ARRANGEMENT OF SIGNALLING OR LIGHTING DEVICES, THE MOUNTING OR SUPPORTING THEREOF OR CIRCUITS THEREFOR, FOR VEHICLES IN GENERAL
- B60Q1/00—Arrangement of optical signalling or lighting devices, the mounting or supporting thereof or circuits therefor
- B60Q1/0076—Switches therefor
-
- B—PERFORMING OPERATIONS; TRANSPORTING
- B60—VEHICLES IN GENERAL
- B60Q—ARRANGEMENT OF SIGNALLING OR LIGHTING DEVICES, THE MOUNTING OR SUPPORTING THEREOF OR CIRCUITS THEREFOR, FOR VEHICLES IN GENERAL
- B60Q11/00—Arrangement of monitoring devices for devices provided for in groups B60Q1/00 - B60Q9/00
-
- H—ELECTRICITY
- H05—ELECTRIC TECHNIQUES NOT OTHERWISE PROVIDED FOR
- H05B—ELECTRIC HEATING; ELECTRIC LIGHT SOURCES NOT OTHERWISE PROVIDED FOR; CIRCUIT ARRANGEMENTS FOR ELECTRIC LIGHT SOURCES, IN GENERAL
- H05B47/00—Circuit arrangements for operating light sources in general, i.e. where the type of light source is not relevant
- H05B47/20—Responsive to malfunctions or to light source life; for protection
- H05B47/21—Responsive to malfunctions or to light source life; for protection of two or more light sources connected in parallel
Definitions
- the present invention concerns a motor vehicle lamp actuation system.
- the disclosure concerns a motor vehicle lamp control method and control apparatus wherein a controller is configured to execute a control program and activate output circuitry comprising a plurality of lamp drivers having inputs coupled to the controller and outputs for actuating multiple motor vehicle lamps.
- Circuitry coupled to the controller transmits lamp actuation commands to the controller, causing the controller to actuate the lamps.
- Overvoltage protection circuitry limits adverse effects of transient signals to avoid damage to the control apparatus.
- One embodiment includes a method for controlling a vehicle lighting system.
- the method monitors an input keypad for at least one input provided by a user and provides an input command to a controller in response to the input.
- the method may also include continuously monitoring an electrical signal associated with each of a plurality of outputs associated with the controller and comparing the monitored electrical signal relative to respective over-current condition thresholds.
- the method may also sequentially control a state of the plurality of outputs with respect to each of a plurality of vehicle lamps.
- FIG. 1 illustrates a schematic perspective of an example of an input device for user actuation of motor vehicle lamps.
- FIG. 1A illustrates a front view of the example of the input device for user actuation of motor vehicle lamps.
- FIGS. 2A and 2B are alternate drive circuits for use with an exemplary embodiment of the invention.
- FIG. 3 illustrates an example of an output control circuit associated with a microprocessor controller in a vehicle light system.
- FIG. 4 illustrates an example of an overview of a vehicle light system.
- FIG. 5 illustrates a flow diagram associated with an overview of a vehicle light system.
- FIGS. 6A and 6B illustrate a flow diagram associated with entering user inputs in a vehicle light system.
- FIGS. 7A and 7B illustrate a flow diagram associated with processing outputs in a vehicle light system.
- FIGS. 8A and 8B illustrate a flow diagram associated with a fault detection and processing system in a vehicle light system.
- An exemplary embodiment provides hardware which prevents damage to a vehicle light system in the event faults occur.
- the exemplary embodiment removes power from lamp drivers during transients and load dumps, thus protecting them from damage.
- the exemplary embodiment allows voltage transients into an exemplary control system without damage occurring.
- FIG. 1 depicts an exemplary embodiment of a user input interface 10 for actuating motor vehicle lamps.
- the input interface 10 includes a keypad 11 , preferably made of an elastomeric material, secured within an enclosure 12 ; and the enclosure 12 preferably made of die cast aluminum mounted to a motor vehicle dashboard (not shown).
- the enclosure 12 preferably made of die cast aluminum mounted to a motor vehicle dashboard (not shown).
- Within an interior of the enclosure 12 there is support circuitry on one or more fully below, that selectively actuates headlamp, stop lamp, and other vehicle lamps whether filament bulbs or Light Emitting Diode (LED) types, collectively referred to as vehicle lamps 14 , of a motor vehicle.
- PCBs printed circuit boards
- FIG. 1A depicts a front view of the user input interface 10 for actuating the motor vehicle lamps 14 .
- the keypad 11 includes nine separate user input keys, each identified with text that describes a respective lamp control function.
- the text for each of the nine user input keys can be illuminated by a backlight LED, as is explained in greater detail in the example of FIG. 6 below.
- each of the nine user input keys can include an indicator LED that can, for example, provide an indication to the user of a current illumination mode.
- the indicator LEDs can be solidly illuminated to indicate that a given illumination mode is currently active, or can be flashed to indicate that the user input interface 10 is awaiting further user input after selecting a given illumination mode.
- the keypad 11 demonstrates, via the text of the user input keys, different illumination modes which the user can initiate.
- the illumination modes can be separated into mutually exclusive primary modes, such as “Blackout Drive,” “Blackout Marker,” “Stop Light,” “Service Drive,” “Park,” and “All Off.” Each of the primary modes can activate a certain combination of the vehicle lamps.
- the illumination modes can also include mutually exclusive auxiliary modes, such as “Panel Dim” and “Panel Bright,” which can be implemented concurrently with one or more of the primary modes.
- the keypad 11 includes a centrally positioned “Enter” key that can allow the user to confirm selection of a selected illumination mode subsequent to pressing the user input key corresponding to the appropriate illumination mode.
- FIG. 4 depicts a block diagram 19 of an exemplary control system that includes a microcontroller 20 which implements in software certain features for enhancing product performance and for providing more operator options.
- the circuitry depicted in FIG. 4 includes a user interface input circuit 22 that issues commands to the microcontroller 20 based on user actuation of user input keys on the keypad 11 .
- the microcontroller 20 issues commands to couple battery voltage at an input 24 from a battery 26 to driver circuits 30 having outputs 32 coupled to the vehicle lamps 14 .
- a junction block 124 is configured to couple control signals from the microcontroller 20 with the driver circuits 30 to provide individual activation and/or control of the output device drivers 110 , 112 , 114 , 116 , 118 , and 120 .
- Power is supplied to the output device drivers 110 , 112 , 114 , 116 , 118 , and 120 by the battery at the input 80 , demonstrated as coupled to all but the driver circuit 116 .
- the driver circuit 116 has an input 117 that can be coupled to a battery voltage through a separate input, such as a vehicle brake pedal.
- An output current associated with each of the output device drivers 110 , 112 , 114 , 116 , 118 , and 120 can be monitored to determine the presence of a fault condition for the respective output device driver.
- the output current from the output device drivers 110 , 112 , 114 , 116 , 118 , and 120 is provided to a junction block 122 via a resistive voltage divider.
- Junction blocks 122 and 124 can be connectors, wire jumpers, ribbon cables and the like. In the example of FIG.
- the resistive voltage divider is demonstrated as a resistor interconnecting each of the output device drivers 110 , 112 , 114 , 116 , 118 , and 120 with the junction block 122 , and a resistor interconnecting each respective terminal of the junction block 122 with ground.
- ADC analog-to-digital converter
- FIG. 5 depicts an embodiment of the present invention that includes a method 200 for controlling a vehicle illumination system.
- the method 200 includes initializing 210 the control system by providing power from a battery to the vehicle illumination system and processing 212 at least one user request via a user interface.
- the method 200 may also include processing 214 at least one output from a vehicle illumination system controller in response to the at least one user request.
- the method 200 may also include continuously monitoring the at least one output and processing 216 at least one fault associated with the at least one output upon determining the presence of the at least one fault.
- the method 200 may also include conserving battery power by entering a sleep mode state 222 in response to not receiving at least one input 220 for a predetermined amount of time.
- the method 200 may further include re-initializing 226 the control system upon determining 224 at least one user input key has been pressed.
- FIGS. 6A and 6B depict a flow-chart of an exemplary embodiment of the present invention that includes a method 250 for controlling inputs to a user interface, such as the user input interface 10 in the example of FIGS. 1 and 1A .
- a user interface such as the user input interface 10 in the example of FIGS. 1 and 1A .
- each of the LEDs of the vehicle are configured to flash for a preset amount of time, such as 500 milliseconds.
- the user input interface backlight LEDs are activated, such that the text on each of the user input keys is illuminated, and thus seen more clearly by a user.
- FIG. 6A demonstrates at a step 252 that a primary illumination mode is set for “All Off” and that no auxiliary illumination modes are activated.
- no auxiliary modes activated and the “All Off” primary mode are a default setting for the vehicle illumination system.
- the method 250 then proceeds to a step 254 , at which the current auxiliary mode LED indicator(s) are held at a steady state, then proceeds to a step 256 , at which the current primary mode LED indicator is held at a steady state.
- the control system is set for a primary illumination mode and/or an auxiliary illumination mode, and is awaiting a user input at the keypad 11 .
- the method 250 determines 257 if a user input key has been pressed. If a user input key has been pressed, then the method 250 proceeds to a decision 258 (depicted on FIG. 6B ), via the linking symbol “C”.
- the method 250 determines 260 if the primary mode is set for “All Off”. If the primary mode is not set for “All Off”, the method 250 returns to the step 256 . If the primary mode is set for “All Off”, the method 250 determines 261 if twenty seconds have elapsed in the “All Off” mode. If twenty seconds have elapsed in the “All Off” mode, the method 250 turns off all LEDs on the user input keypad 262 . If twenty seconds have not elapsed in the “All Off” mode, the method 250 determines 263 if the “All Off” key was pressed. If the “All Off” key was not pressed, the method 250 returns to the step 254 . If the “All Off” key was pressed, the method 250 turns off all LEDs on the user input keypad 262 . The method 250 then enters a standby mode and awaits another key press before re-initializing the user input keypad 11 again.
- FIG. 6A demonstrates deactivation of the user input keypad 11 .
- FIG. 6A demonstrates that the user input keypad 11 is deactivated upon pressing the “All Off” key, or through twenty seconds of inaction after initializing the user input keypad 11 .
- FIG. 6B demonstrates changing modes through selecting a mode via the user input keypad 11 .
- the method 250 determines 258 if the input (i.e., the pressed key) corresponds to a primary mode. If the input corresponds to a primary mode, the method 250 proceeds to the decision 264 . If the input does not correspond to a primary mode, the selected input corresponds to an auxiliary mode and the method 250 proceeds to a determination of whether the primary mode is set for “All Off”. If the primary mode is set for “All Off”, the method 250 returns to the step 254 on FIG. 6A , via the linking symbol “D”. If the primary mode is not set for “All Off”, the method 250 determines if the input (i.e., the pressed key) corresponds to the present auxiliary mode.
- the present auxiliary mode is set to off (i.e., deactivated).
- an auxiliary mode is deactivated by re-selecting it on the keypad 11 .
- the selected auxiliary mode provided via the input, is set as the present auxiliary mode. The method 250 then returns to the step 254 on FIG. 6A , via the linking symbol “D”.
- the method 250 determines if the provided input corresponds to the present primary mode. If the provided input corresponds to the present primary mode, the method 250 returns to the decision 260 on FIG. 6A , via the linking symbol “B”. If the provided input does not correspond to the present primary mode, the method 250 proceeds to the step 266 , at which the selected mode key and the “Enter” key indicator LEDs begin to flash. The method 250 then determines if the “Enter” key has been pressed. If the “Enter” key has been pressed, the selected primary mode, provided via the input, is set as the present primary mode, and the method 250 returns to the step 254 on FIG. 6A , via the linking symbol “D”.
- the above described method 250 in the example of FIG. 6B demonstrates that auxiliary modes can be activated and deactivated without pressing the “Enter” key.
- the above described method 250 also demonstrates that, upon selecting a primary mode, a delay of five seconds without pressing the “Enter” key results in the user input interface returning to the previously active primary mode. However, during the five second delay, a different primary mode can be selected without having to confirm the previous selection via the “Enter” key or having to wait for the five seconds to elapse.
- the exemplary embodiment demonstrated by the method 250 in the example of FIG. 6 provides a user-friendly mode selection interface that is forgiving of a mistakenly selected primary mode.
- FIGS. 7A and 7B depict an exemplary embodiment of the present invention that includes a method 300 for controlling outputs, such as in response to receiving inputs at the user input interface 10 of FIGS. 1 and 1A .
- the method 300 begins by determining whether the present primary mode is set for “All Off”. If the present primary mode is not set for “All Off”, the method 300 proceeds to a decision 302 . If the present primary mode is set for “All Off”, the method 300 determines if all of the outputs of the vehicle illumination system are off. If all of the outputs of the vehicle illumination system are not off, the method 300 proceeds to the decision 302 . If all of the outputs of the vehicle illumination system are off, the method 300 ends based on all of the outputs being switched off as a result of the primary mode being set to “All Off”.
- the controller determines whether the state of the headlamps (i.e., activated or deactivated) match the current primary mode.
- the current primary mode For example, one or more of the primary modes may include activation of the headlamps of the vehicle. If the state of the headlamps matches the current primary mode, the method 300 proceeds to a decision 304 . If the state of the headlamps does not match the current primary mode, the method 300 determines whether the headlamps should be activated and that no fault condition is sensed. If the headlamps should not be activated, or are in a fault condition, the method 300 deactivates the headlamps and proceeds to the decision 304 . If the headlamps should be activated, and are not in a fault condition, the method 300 proceeds to the step 306 (depicted in FIG. 7B ) via the linking symbol “E”.
- the controller determines whether the state of the stop lamps (i.e., enabled or disabled) match the current primary mode.
- the primary modes may include enablement of the stop lamps of the vehicle, such that the stop lamps are activated based on a user input (e.g., pressing a brake pedal). If the state of the stop lamps matches the current primary mode, the method 300 proceeds to the step 308 . If the state of the stop lamps does not match the current primary mode, the method 300 determines whether the stop lamps should be activated and not in a fault condition. If the stop lamps should be activated, and are not in a fault condition, the method 300 proceeds to the step 310 on FIG. 7B via the linking symbol “F”.
- the method 300 disables the stop lamps and proceeds to the step 308 .
- the method 300 sets the remaining output conditions associated with the vehicle lamps at 308 based on the current primary and/or auxiliary mode and the current fault conditions and ends. Therefore, the method 300 ends by individually activating or deactivating the remaining vehicle lamps based on the currently set primary and/or auxiliary mode, and based on which of the vehicle lamps are faulted.
- FIG. 7B demonstrates activation of the headlamps and/or the stop lamps of the vehicle.
- the method 300 initiates a soft start of the filament type headlamps at 306 in response to the state of the headlamps being set for activation absent a fault condition.
- Activation of the headlamps of a vehicle can result in a high inrush current draw (e.g., 80 amps or more), such that instantaneous current flow of the illumination system can exceed a predetermined threshold of the headlamps and/or a summation over-current threshold of the illumination system as a whole.
- the current draw of the headlamps can be the highest at lower temperatures of the headlamp filaments.
- the microcontroller 20 incorporates an algorithm for soft starting the headlamp drive, such as the drive 110 in the example of FIG. 3 .
- a temperature sensing device such as a thermistor may be used to determine an approximate ambient temperature. The temperature sensor will send temperature information to the microcontroller 20 so that the microcontroller can determine if soft starting the lamps is required.
- a typical temperature threshold is 10° F., below which soft start will be enabled.
- the microcontroller 20 commands the output drive 110 of the headlamps to provide a pulsed signal to the headlamps, such that the headlamps receive current pulses.
- the pulse rate of the pulsed signal begins at a high frequency to preheat the filament in the headlamp bulbs.
- the on-state of the pulsed signal is extended while the off-state of the pulsed signal is steadily reduced in frequency, such that the current pulses to the headlamps become longer in duration. Therefore, the current draw of the headlamps is steadily reduced until the current is low enough to fully activate the output drive 110 (i.e., the frequency of the off-state is reduced to zero). Accordingly, because the temperature of the headlamp filaments is gradually increased by the current pulses prior to full activation of the headlamps, the inrush current of the headlamps is greatly reduced.
- the method 300 determines if the soft start of the headlamps is complete. For example, the method 300 determines if the inrush current associated with headlamps is at an acceptable level, or determines that a temperature associated with the headlamp filaments is at a level that can result in an acceptable level of inrush current. If the soft start of the headlamps is complete, the method 300 fully activates the headlamps, such as by setting the frequency of the off-state of the pulsed signal equal to zero, and sets the state of the headlamps to “on”. Upon full activation of the headlamps, or upon the soft start of the headlamps being incomplete, the method 300 ends by returning to FIG. 7A via the linking symbol “G”.
- vehicle lamps 14 can be either filament type lamps or light emitting diode (LED) type lamps.
- a particular application may have 100% of one of the types or any combination of the different types of lamps.
- the LED type lamps do not exhibit cold filament characteristics typical of filament type lamps. They have a fairly constant current draw regardless of temperature. The LED type lamps also have significantly lower current draw than filament type lamps.
- a vehicle may have either type or a combination of filament type and LED type lamps another exemplary embodiment will alleviate an over current fault from being generated due to high inrush current, by having the microcontroller 20 increase an over current fault threshold by a given or calculated amount.
- the threshold will stay at its increased value for a predetermined or calculated amount of time to ensure that inrush current is over and then microcontroller 20 will reduce the threshold to a lower value.
- the temporary increase in over current threshold eliminates false over current faults.
- the temporary increase in over current threshold does not adversely effect operation. Therefore any combination of lamp types can be used without any adverse effects.
- Typical current draw per LED lamp is in the 25 mA to 100 mA range. It is not uncommon to arrange many individual LED lamps into an array to form a lamp assembly. The lamp assemblies are located on vehicles in typical locations. LED type lamps are very efficient in their use of power to produce light. In LED arrays typical of vehicular lamp assemblies, the many individual LED devices that form the lamp assembly provide for a very noticeable display.
- a known issue with the high efficiency of the LED lamps 14 and solid state driver circuitry such as 110 is that very small amounts of current flow, less than 100 uA, will cause the LED array to produce light. Small amounts of leakage current are typical of certain electronic drivers such as 110 . This can be undesirable in many circumstances.
- various methods may be employed including adding passive components such as a resistor 113 on the driver output 111 to shunt leakage current through some path other than through the LED. Typically this path is vehicle battery ground. Alternately an active clamp may be used such as a transistor 115 , which could be a Field Effect or bipolar type, either of which will be on when the driver is off, so that the leakage current will be shunted through a path other than the LED.
- passive components such as a resistor 113 on the driver output 111 to shunt leakage current through some path other than through the LED.
- this path is vehicle battery ground.
- an active clamp may be used such as a transistor 115 , which could be a Field Effect or bipolar type, either of which will be on when the driver is off, so that the leakage current will be shunted through a path other than the LED.
- the method 300 In response to the state of the stop lamps being set for enablement absent a fault condition, the method 300 enables the stop lamps and sets the state of the stop lamps to “on” at the step 310 . It is to be understood that the stop lamps may require an additional input from a user, such as via a brake pedal, to activate the stop lamps once the stop lamps are enabled by the microcontroller 20 . However, the state of the stop lamps corresponds to an enablement setting associated with the current primary and/or auxiliary illumination mode, and are thus set to “on” regardless of actual activation of the stop lamps. The method 300 then ends by returning to FIG. 7A via the linking symbol “G”.
- the above described method 300 describes a manner in which headlamps and stop lamps are activated and/or enabled separately from other lamps in the vehicle illumination system.
- FIGS. 7A and 7B describe soft starting of the headlamps and enablement of the stop lamps, as opposed to direct activation.
- FIGS. 8A and 8B depict an exemplary embodiment of the present invention that includes a method 350 for processing faults, such as in response to one of an over-current condition associated with an individual output device driver or a summation over-current condition associated with the vehicle illumination system.
- the method 350 can be applicable to a given one of the output device drivers 110 , 112 , 114 , 116 , 118 , and 120 .
- the vehicle illumination system may implement the method 350 for each of the output device drivers 110 , 112 , 114 , 116 , 118 , and 120 sequentially, or in separately running processes concurrently. Therefore, in the example of FIGS.
- the “selected lamp(s)” refers to the lamp(s) corresponding to a given one of the output device drivers 110 , 112 , 114 , 116 , 118 , and 120 .
- the method 350 begins by determining whether the selected lamps are activated based on the selected illumination mode (e.g., primary and/or auxiliary). If the selected lamps are not activated based on the selected illumination mode, the method 350 clears faults associated with the selected lamps and proceeds to the step 352 , at which the method 350 processes the remaining outputs associated with one or more of the output device drivers 110 , 112 , 114 , 116 , 118 , and 120 before ending. If the selected lamps are activated based on the selected illumination mode, the method 350 determines if the current is above a limit for the device.
- the selected illumination mode e.g., primary and/or auxiliary
- the method 350 determines if a summation over-current condition exists for the vehicle illumination system. For example, the method 350 determines if the total aggregate output current associated with all vehicle lamps exceeds a summation over-current threshold. In an exemplary embodiment, the summation over-current threshold is less than a sum of the over-current thresholds associated with each of the individual vehicle lamps. If a summation over-current condition exists for the vehicle illumination system, the method 350 proceeds to the step 356 on FIG. 8B via the linking symbol “I”. If a summation over-current condition does not exist for the vehicle illumination system, the method 350 determines if the output associated with the specific output device driver is faulted.
- one of the output device drivers 110 , 112 , 114 , 116 , 118 , and 120 can become faulted based on an over-current condition, as demonstrated below in the example of FIG. 8B .
- the method 350 proceeds to the decision 358 on FIG. 8B via the linking symbol “J”. If the output associated with the specific output device driver is not faulted, the method 350 determines if the output is below the current limit for the device, such as based on a normal operating condition for the device. If the output is below the current limit for the device, the method 350 proceeds to the step 358 on FIG. 8B via the linking symbol “K”.
- the method 350 proceeds to the step 352 , such that the method 350 begins again with the next one or more of the output device drivers 110 , 112 , 114 , 116 , 118 , and 120 .
- the method 350 described above regarding the example of FIG. 8A demonstrates a continuous over-current diagnostic check, both for an over-current associated with an individual output device driver and for a summation over-current.
- the example of FIG. 8B demonstrates how fault conditions are set and cleared.
- the method 350 determines at 354 how long the device should remain in an over-current condition based on a magnitude of the current. As an example, the amount of time the device should remain in the over-current condition is inversely proportional to the magnitude of the current, such that greater amounts of current results in less time in the over-current condition. The method 350 then determines if the output device driver should go to a faulted state based on the amount of time determined in the step 354 .
- the method 350 could set a timer threshold based on the amount of time determined in the step 354 , such that the method 350 determines if the output device driver should go to the faulted state based on whether an elapsed time in the over-current condition exceeds the timer threshold. If the output device driver should not go to the faulted state, for example, as a result of the current dropping below the over-current limit for the device before expiration of the timer, the method 350 proceeds to the step 352 via the linking symbol “L”.
- the method 350 proceeds to the step 356 , at which the output device driver is disabled, marked as faulted, and a retry timer associated with the output device driver is started. The method 350 then proceeds to the step 352 via the linking symbol “L”.
- the microcontroller 20 includes an algorithm that provides diagnostics for informing the user that an output fault exists by flashing an appropriate indicator (e.g., fault LED for a specific output).
- the algorithm in the exemplary embodiment uses voltage and current feedback to determine the nature of the fault, such that the microcontroller 20 determines if the specific output device driver has an output fault that is an open circuit fault (e.g., from a burned-out or open lamp) or short circuit fault.
- This element of diagnostics provides real time feedback to the operator when a problem occurs, such that the microcontroller 20 determines if a specific lamp is open or shorted based on monitoring the voltage and current parameters on each output.
- a fault indicator LED for the output is illuminated and flashed when an appropriate fault condition is present.
- the type of fault is identified by the rate of flashing, such as a short circuit condition represented by a fast pulse and an open circuit condition represented by a slow pulse.
- the retry timer at the step 356 is implemented as a timer that is configured for clearing a fault condition.
- the retry timer is a directly proportional timer.
- the retry timer is thus a timer for recovering from a fault condition that has a variable timing threshold based on the amount of the over-current.
- the retry timer is specific to a given one of the faulted outputs, thus allowing each of the faulted outputs to recover individually.
- the vehicle illumination system can recover from faults at a safe rate, as opposed to repeated retry attempts for all faulted outputs in short periods of time. Therefore, excess heat damage to the vulnerable circuit components, such as the output device driver, and/or wire harness assemblies is mitigated.
- the method 350 determines 358 whether the retry timer has expired. If the retry timer has expired, the timer is reset and the output is enabled, thus clearing the fault condition. Upon clearing the fault, or if the retry timer has not expired, the method 350 proceeds to the step 352 via the linking symbol “L”.
- the method 350 informs the user of the problem at the step 360 by illuminating an indicator LED, or by sending a message via communications protocols such as SAE J1939 or other unique protocols. The message transmission may be through the flashing of an indicator light or through an electrical connection through the device connector pins.
- the problem could include an open circuit condition, such as a burned-out lamp corresponding to the given output device driver.
- the method 350 then proceeds to the step 352 via the linking symbol “L”.
- the vehicle illumination system can implement sequential activation and/or deactivation of vehicle lamps to provide over-current protection.
- the sequential activation and/or deactivation can be implemented separate from or in conjunction with the method 350 .
- the microcontroller 20 staggers activation of vehicle lamps to reduce inrush current, thus preventing a summation over-current condition. For example, in response to a user selecting a primary and/or auxiliary illumination mode via the user input interface 10 , a number of vehicle lamps 14 may be commanded by the microcontroller 20 to be activated. Each of the vehicle lamps 14 may draw an inrush current, such that, when activated concurrently, the aggregate amount of the inrush current can exceed the summation over-current threshold for the vehicle illumination system. To prevent the excessive inrush current of all of the vehicle lamps at once, the microcontroller 20 staggers the output turn-on sequence, such that each of the vehicle lamps is activated individually in a rapid sequence. As a result, the sequential activation of the vehicle lamps provides a gradual current draw to avoid a bulk inrush of current which can stress other electrical components on the vehicle (e.g., the alternator), and cause a nuisance summation over-current condition.
- the microcontroller 20 staggers activation of vehicle lamps to reduce in
- the microcontroller 20 sequentially deactivates vehicle lamps based on a priority structure in a load-shedding procedure, such that over-current conditions can be avoided and/or cleared. Sequentially, upon a summation over-current condition, the microcontroller 20 begins load-shedding, such that one or more of the output drives are deactivated to reduce the aggregate output current associated with the vehicle lamps.
- the microcontroller 20 incorporates an algorithm for setting the priority of output drives from highest to lowest based on considerations of safety. As a result, the most important output drives remain active in the event of a summation over-current condition. For example, the set priority dictates that the least needed output drives are deactivated, leaving the most important drives (e.g., headlamps) active.
- the load-shedding priority can be set in a variety of ways.
- the priority of load-shedding is determined automatically by the microcontroller 20 .
- the load-shedding priority is predefined by the user or is programmed into the microcontroller 20 . As such, upon the occurrence of a summation over-current condition, the lowest priority output is deactivated first and the summation current re-checked.
- the microcontroller 20 implements a load-shedding priority that is a combination of the prior two examples. As such, priority is set based on individual over-current levels, with predefined exceptions (e.g., headlamps) being allowed to continue being activated, even if experiencing an individual over-current condition. Regardless of the priority scheme implemented, the load-shedding priority embodiment allows systematic disabling of output drives until the summation over-current condition clears for safer operation.
Landscapes
- Engineering & Computer Science (AREA)
- Mechanical Engineering (AREA)
- Lighting Device Outwards From Vehicle And Optical Signal (AREA)
Abstract
Description
Claims (33)
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US12/614,866 US8089350B2 (en) | 2006-08-25 | 2009-11-09 | Vehicle light system |
US13/339,599 US8633813B2 (en) | 2006-08-25 | 2011-12-29 | Vehicle light system |
Applications Claiming Priority (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US84030306P | 2006-08-25 | 2006-08-25 | |
US11/649,692 US7616108B2 (en) | 2006-08-25 | 2007-01-04 | Vehicle light system |
US12/614,866 US8089350B2 (en) | 2006-08-25 | 2009-11-09 | Vehicle light system |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/649,692 Continuation-In-Part US7616108B2 (en) | 2006-08-25 | 2007-01-04 | Vehicle light system |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/339,599 Continuation-In-Part US8633813B2 (en) | 2006-08-25 | 2011-12-29 | Vehicle light system |
Publications (2)
Publication Number | Publication Date |
---|---|
US20100085179A1 US20100085179A1 (en) | 2010-04-08 |
US8089350B2 true US8089350B2 (en) | 2012-01-03 |
Family
ID=42075347
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/614,866 Expired - Fee Related US8089350B2 (en) | 2006-08-25 | 2009-11-09 | Vehicle light system |
Country Status (1)
Country | Link |
---|---|
US (1) | US8089350B2 (en) |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20120119898A1 (en) * | 2006-08-25 | 2012-05-17 | Narton Corporation | Vehicle light system |
US9374871B2 (en) | 2012-08-02 | 2016-06-21 | Valeo Vision | Method and system for controlling a plurality of light modules in a light and/or signaling system based on failure event of the plurality of light module |
Families Citing this family (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8816868B2 (en) * | 2011-06-06 | 2014-08-26 | Apple Inc. | Adaptive low-battery warnings for battery-powered electronic devices |
US20140313027A1 (en) * | 2013-04-19 | 2014-10-23 | Fenton C. Johnson | Headlight status display system for automobile |
DE102016011815B3 (en) * | 2016-10-05 | 2018-02-15 | IAD Gesellschaft für Informatik, Automatisierung und Datenverarbeitung mbH | Control gear with staggered overvoltage and overcurrent protection for the control of intelligent light sources and devices as well as light sources with this control gear |
Citations (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4611291A (en) * | 1983-11-10 | 1986-09-09 | General Signal Corp. | Vital interface system for railway signalling |
US4841198A (en) | 1987-10-19 | 1989-06-20 | Nartron Corporation | Head lamp control method and apparatus, with PWM output regulation |
US4866390A (en) | 1987-08-11 | 1989-09-12 | Butchko Joseph R | Vehicle light testing system for testing a plurality of lights using a scanning sequence |
US5247280A (en) | 1991-08-01 | 1993-09-21 | Cooper Industries, Inc. | Combination vehicle flasher having first and second flash rates and duty rates |
US5517064A (en) | 1993-07-15 | 1996-05-14 | Alps Electric Co., Ltd. | Protective device for lighting system used in motor vehicle |
US5629680A (en) | 1995-12-11 | 1997-05-13 | Makhija; Surender K. | Vehicle current drain tester with memory saver |
US6002330A (en) | 1999-02-15 | 1999-12-14 | J. W. Speaker Corporation | Control system for vehicle lighting |
US6160475A (en) | 1998-05-21 | 2000-12-12 | Sidler Gmbh & Co. | Lighting device in the door of a vehicle |
US7616108B2 (en) * | 2006-08-25 | 2009-11-10 | Nartron Corporation | Vehicle light system |
-
2009
- 2009-11-09 US US12/614,866 patent/US8089350B2/en not_active Expired - Fee Related
Patent Citations (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4611291A (en) * | 1983-11-10 | 1986-09-09 | General Signal Corp. | Vital interface system for railway signalling |
US4866390A (en) | 1987-08-11 | 1989-09-12 | Butchko Joseph R | Vehicle light testing system for testing a plurality of lights using a scanning sequence |
US4841198A (en) | 1987-10-19 | 1989-06-20 | Nartron Corporation | Head lamp control method and apparatus, with PWM output regulation |
US5247280A (en) | 1991-08-01 | 1993-09-21 | Cooper Industries, Inc. | Combination vehicle flasher having first and second flash rates and duty rates |
US5517064A (en) | 1993-07-15 | 1996-05-14 | Alps Electric Co., Ltd. | Protective device for lighting system used in motor vehicle |
US5629680A (en) | 1995-12-11 | 1997-05-13 | Makhija; Surender K. | Vehicle current drain tester with memory saver |
US6160475A (en) | 1998-05-21 | 2000-12-12 | Sidler Gmbh & Co. | Lighting device in the door of a vehicle |
US6002330A (en) | 1999-02-15 | 1999-12-14 | J. W. Speaker Corporation | Control system for vehicle lighting |
US7616108B2 (en) * | 2006-08-25 | 2009-11-10 | Nartron Corporation | Vehicle light system |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20120119898A1 (en) * | 2006-08-25 | 2012-05-17 | Narton Corporation | Vehicle light system |
US8633813B2 (en) * | 2006-08-25 | 2014-01-21 | Uusi, Llc | Vehicle light system |
US9374871B2 (en) | 2012-08-02 | 2016-06-21 | Valeo Vision | Method and system for controlling a plurality of light modules in a light and/or signaling system based on failure event of the plurality of light module |
Also Published As
Publication number | Publication date |
---|---|
US20100085179A1 (en) | 2010-04-08 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US8633813B2 (en) | Vehicle light system | |
US7616108B2 (en) | Vehicle light system | |
US20080122365A1 (en) | Method of Supplying Pulsed Power to Light Bulbs in Motor Vehicles | |
US8089350B2 (en) | Vehicle light system | |
US7852203B2 (en) | Vehicular flasher unit operative to provide a heartbeat flasher scheme | |
US9475424B2 (en) | Adaptive shunt for pulsing brake light | |
EP1830607B1 (en) | Lighting and systems for controlling lighting | |
US8120273B2 (en) | Light control system with PWM duty cycle control using current signal feedback | |
CN101662867B (en) | Dimming control system for vehicular lamp | |
JP4318300B2 (en) | Lighting control device and failure detection device | |
AU643782B2 (en) | Circuitry arrangement for a motor vehicle headlight | |
KR101945589B1 (en) | Apparatus and method for controlling power supply | |
AU2005325009B2 (en) | Device for the controlled switching of a lamp, use of the device and corresponding operating method | |
GB2371689A (en) | Modifying current waveform and detecting failure in non-incandescent lighting system | |
CN210431989U (en) | Car light overtemperature protection system and vehicle with same | |
US20150224922A1 (en) | Brake light drive control device | |
CN109792816B (en) | Regulation of sequentially operated light sources and apparatus for performing the method | |
JP7317238B2 (en) | circuit system | |
JP5948202B2 (en) | Energization control circuit for vehicle turn lamp unit and energization control method for vehicle turn lamp unit | |
JP2003072487A (en) | Onboard power source control device | |
JP2007287476A (en) | Vehicular lamp lighting circuit | |
JP2004022370A (en) | Display device | |
KR102027214B1 (en) | spike-relief power control device for sensor lights which having constant voltage constant current converter | |
JP6209848B2 (en) | Vehicle lighting | |
JP2010507185A (en) | Method for driving a PTC electrical load element |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: NARTRON CORPORATION,MICHIGAN Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:SHANK, DAVID, MR.;COX, EDWARD, MR.;WASHELESKI, JOHN, MR.;REEL/FRAME:023490/0745 Effective date: 20091109 Owner name: NARTRON CORPORATION, MICHIGAN Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:SHANK, DAVID, MR.;COX, EDWARD, MR.;WASHELESKI, JOHN, MR.;REEL/FRAME:023490/0745 Effective date: 20091109 |
|
AS | Assignment |
Owner name: UUSI, LLC,MICHIGAN Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:NARTRON CORPORATION;REEL/FRAME:024146/0292 Effective date: 20100323 Owner name: UUSI, LLC, MICHIGAN Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:NARTRON CORPORATION;REEL/FRAME:024146/0292 Effective date: 20100323 |
|
ZAAA | Notice of allowance and fees due |
Free format text: ORIGINAL CODE: NOA |
|
ZAAB | Notice of allowance mailed |
Free format text: ORIGINAL CODE: MN/=. |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
FPAY | Fee payment |
Year of fee payment: 4 |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 8TH YR, SMALL ENTITY (ORIGINAL EVENT CODE: M2552); ENTITY STATUS OF PATENT OWNER: SMALL ENTITY Year of fee payment: 8 |
|
FEPP | Fee payment procedure |
Free format text: MAINTENANCE FEE REMINDER MAILED (ORIGINAL EVENT CODE: REM.); ENTITY STATUS OF PATENT OWNER: SMALL ENTITY |
|
LAPS | Lapse for failure to pay maintenance fees |
Free format text: PATENT EXPIRED FOR FAILURE TO PAY MAINTENANCE FEES (ORIGINAL EVENT CODE: EXP.); ENTITY STATUS OF PATENT OWNER: SMALL ENTITY |
|
STCH | Information on status: patent discontinuation |
Free format text: PATENT EXPIRED DUE TO NONPAYMENT OF MAINTENANCE FEES UNDER 37 CFR 1.362 |
|
FP | Lapsed due to failure to pay maintenance fee |
Effective date: 20240103 |