Daytime running light override for vehicle headlight control

Abstract

To provide systems for controlling a high beam headlight of a vehicle.SOLUTION: Systems, methods and devices for controlling a high beam headlight 42 of a vehicle 10. One system includes a high beam headlight mounted on a vehicle, a sensor mounted on the vehicle 60, 62, and an electronic control unit 200. The electronic control unit is configured to receive an input to turn on the high beam headlight, determine a status of an override of an automatic high beam function of the vehicle, and determine a current time of day based on data received from the sensor. In response to the current time of day being daylight and the status of the override being enabled, the electronic control unit is configured to override the automatic high beam function to allow the high beam headlight to be turned on based on the input while maintaining a status of the automatic high beam function as enabled.SELECTED DRAWING: Figure 1

Description

Technical Field

[0001] Aspects described in this specification relate to systems and methods for controlling a vehicle lighting system, such as a high beam system of a motorcycle.

Background Art

[0002] Vehicles are equipped with one or more headlamps, such as one or more low beam headlamps and one or more high beam headlamps. The headlamp may be controlled in response to user input (e.g., operation of an actuator or other input mechanism, i.e., a button, lever, switch, etc.). There are also vehicles equipped with automatic headlamp control. Among automatic headlamp controls, an electronic control unit included in the vehicle is configured to control the operation of the headlamp in response to data collected via one or more sensors, such as one or more vehicle sensors. For example, a vehicle may be equipped with an automatic high beam (AHB) control or function, and the automatic high beam (AHB) control or function is configured to automatically turn off the high beam headlamp (i.e., without user operation) in response to the detection of one or more driving conditions, such as when the high beam is not effective or driving conditions that may affect other vehicles.

Summary of the Invention

[0003] Aspects described in this specification provide a system and method for overriding automatic headlamp control, such as an AHB function, for specific driving conditions without requiring disabling of the control. For example, in one aspect, a system is provided. The system includes a high beam headlamp mounted on the vehicle, a sensor mounted on the vehicle, an electronic control unit, configured to receive an input to turn on the high beam headlamp, configured to determine a status of overriding the automatic high beam function of the vehicle, It is configured to determine the current time based on data received from the sensor. It includes an electronic control unit configured to override the automatic high beam function in response to the current time being daytime and the override status being enabled, allowing the high beam headlights to be turned on based on input while maintaining the automatic high beam function status in an enabled state.

[0004] In another embodiment, a method for controlling the high-beam headlights of a vehicle is provided. The method is: In the vehicle's electronic control unit, the steps include receiving an input to turn on the high-beam headlights, The electronic control unit determines the status of the vehicle's automatic high beam function override, The electronic control unit performs the steps of determining the current time and The method includes the step of enabling the electronic control unit to override the automatic high beam function in response to the current time being daytime and the override status being enabled, thereby enabling the high beam headlights to be turned on based on input while maintaining the status of the automatic high beam function in an enabled state.

[0005] In yet another embodiment, a computer program (non-temporary computer-readable medium) is provided which includes instructions that, when executed by one or more electronic processors, perform a set of functions. The set of functions are: To illuminate the vehicle's high-beam headlights, it receives an input, Determine the override status of the vehicle's automatic high beam function, Determining the current time, The system includes the ability to override the automatic high beam function in response to the current time being daytime and the override status being enabled, and to turn on the high beam headlights based on input while maintaining the automatic high beam function status in an enabled state. [Brief explanation of the drawing]

[0006] Along with the following detailed description, the accompanying drawings, in which similar reference figures point to the same or functionally similar elements throughout separate figures, are incorporated herein and constitute part of this specification, and further serve to illustrate various embodiments and to explain the various principles and advantages of those embodiments.

[0007] [Figure 1] This is a side view of a motorcycle in several configurations. [Figure 2] The electronic control unit of the motorcycle shown in Figure 1 is schematically illustrated in several embodiments. [Figure 3] This flowchart shows a method for controlling the high-beam headlights of the motorcycle shown in Figure 1, relating to several embodiments. [Figure 4] This flowchart illustrates another method for controlling the high-beam headlights of the motorcycle shown in Figure 1, relating to another embodiment. [Modes for carrying out the invention]

[0008] One or more embodiments are described and illustrated in the following description and accompanying drawings. These embodiments are not limited to the specific details provided herein and may be modified in various ways. Furthermore, other embodiments not described herein may exist. Also, a function described herein as being performed by a single component may be performed by multiple components in a distributed manner. Similarly, a function performed by multiple components may be integrated and performed by a single component. Likewise, a component described as performing a particular function may perform additional functions not described herein. For example, a device or structure “configured” in a certain manner may be configured in at least that manner, but may be configured in a manner not described herein. Furthermore, some examples described herein may include one or more electronic control units or controllers. For example, these electronic control units or controllers may be configured with one or more general-purpose or specialized electronic processors, such as microprocessors, digital signal processors, customized processors, and field-programmable gate arrays (FPGAs), and unique stored program instructions (including both software and firmware) that control one or more electronic control units or controllers to perform the functions described herein.

[0009] Similarly, embodiments described herein may be implemented as non-temporary computer-readable media for storing instructions executable by one or more electronic processors in order to perform the described functionality. As used in this application, “non-temporary computer-readable media” includes all computer-readable media but does not consist of temporary, propagating signals. Accordingly, non-temporary computer-readable media may include, for example, ROM (Read Only Memory), RAM (Random Access Memory), register memory, processor cache, or any combination thereof.

[0010] Furthermore, the expressions and terms used herein are for illustrative purposes only and should not be considered restrictive. For example, the use herein of “includes,” “contains,” “equips,” “has,” and their variations means including the matters listed thereafter and their equivalents, and additional matters. The terms “connected” and “joined” are used broadly and include both direct and indirect connections and combinations. Furthermore, “connected” and “joined” are not limited to physical or mechanical connections or combinations, but may include electrical connections or combinations, whether direct or indirect. Furthermore, relational terms such as first and second, upper and lower are used herein solely to distinguish one entity or action from another, and do not necessarily require or imply any actual relationship or order between such entities or actions.

[0011] As described above, the embodiments described herein provide systems and methods for controlling vehicle headlight assemblies, such as high-beam headlights on motorcycles. While embodiments are described herein in relation to motorcycles, the components and associated functionalities described herein are not limited to motorcycles and may be used in any type of vehicle (e.g., mopeds, electric bicycles, tricycles, passenger cars, semi-trucks, etc.).

[0012] Figure 1 is a side view of a motorcycle 10 in several embodiments. The motorcycle 10 includes a front wheel 14, a rear wheel 18, and a main frame 22. The front wheel 14 and the rear wheel 18 engage with the road surface 24, which may be, for example, a paved road or a gravel road. The main frame 22 includes, or is coupled to, a front fork 26 supporting the front wheel 14 and a rear swingarm supporting the rear wheel 18. The motorcycle 10 shown in Figure 1 may be powered by an internal combustion engine. However, the embodiments described herein are not limited to motorcycles having an engine, and the systems and methods described herein may be used in electric motorcycles, hybrid motorcycles, or vehicles powered via other power sources or combinations thereof.

[0013] The front fork 26 is configured to rotate in order to change the orientation of the front wheel 14 relative to the rear wheel 18. The rotation of the front fork 26 is controlled via a pair of handlebars 38. The pair of handlebars 38 provide the user with an area to grasp and rotate the front fork 26 to the desired orientation. Furthermore, the handlebars 38 include one or more input mechanisms (e.g., actuators, touchscreens, microphones, etc.) that allow the user to operate various components and systems of the motorcycle 10, such as the high-beam headlights 42 mounted on the vehicle. This may be included as part of a headlight assembly that further includes low-beam headlights, one or more turn signals, fog lights, running lights, or a combination thereof.

[0014] For example, as shown in Figure 1, one or both handlebars 38 may include a lighting control or input mechanism 46, which may be a button, knob, temporary switch, lever, joystick, touchscreen, microphone (e.g., for voice activation), etc. As will be explained in more detail with respect to Figure 2, input received via the lighting input mechanism 46 is supplied to an electronic control unit (ECU) 200 of the motorcycle 10 configured to control the high-beam headlights 42. Control of the high-beam headlights 42 may include turning the high-beam headlights 42 on or off. In some embodiments, the ECU 200 is also configured to control other lights, such as low-beam headlights, using received user input (e.g., via the lighting input mechanism 46 or other input mechanisms). In other embodiments, the motorcycle 10 may include a separate ECU configured to control the other lights of the motorcycle 10.

[0015] Although not shown in Figure 1, the motorcycle 10 further includes one or more user interfaces that provide information to the user. The user interface may be mounted on the motorcycle 10 and may include one or more liquid crystal displays (LCDs), lights or indicators, light-emitting diodes (LEDs), touchscreens or head-up displays, speakers, vibration devices, etc., and may provide the user with information about the current operating state of the motorcycle 10 (e.g., speed, direction of travel, mileage, etc.), the state of various vehicle components (e.g., whether the high-beam headlights 42 are illuminated or not, or a combination thereof). The user interface may provide information to the user in a visual form, an audible form, a tactile form, or a combination thereof. For example, the user interface may include a speaker configured to provide audio output, a vibration device configured to provide tactile output, or a combination thereof.

[0016] Furthermore, one or more of the provided user interfaces may function as input mechanisms that receive user input (second input). For example, if the user interface includes a touchscreen, the user interface may present one or more graphical user interfaces, each graphical user interface including one or more selection mechanisms that the user can select (e.g., touch, drag, drop) to provide input. Similarly, in some embodiments, the motorcycle 10 may be equipped with microphones, cameras, or other sensors to receive audible, visual, or tactile input from the user. Accordingly, the term “input mechanism” as used herein includes a physical device or actuator operable by the user, a touchscreen, a microphone, a camera, or any other device located anywhere on the motorcycle 10 and configured to receive input from the user. In fact, in some embodiments, the “input mechanism” as used herein includes, for example, a mobile phone, a tablet computer, a smartwatch or other wearable, a key fob, or a portable device configured to communicate with the communication interface of the motorcycle 10 to receive user input (e.g., configuration settings or input).

[0017] Furthermore, the motorcycle 10 includes one or more sensors. For example, as shown in Figure 1, the motorcycle 10 may include a forward-facing camera 60 (e.g., mounted on the front fairing of the motorcycle 10) configured to collect image data of the environment surrounding the motorcycle 10, and a light sensor 62 (e.g., mounted on the front fairing or other upward-facing surface of the motorcycle 10) configured to measure the amount of light in the environment surrounding the motorcycle 10 (e.g., ambient light level), or a combination thereof. The camera 60 may include a custom imager camera for in-vehicle vision applications and may be configured to detect the daytime operating state of the vehicle based on luminance values, etc. In some embodiments, the light sensor 62 is positioned upward (e.g., towards the sky or away from the road surface 24). As shown in Figure 1, the motorcycle 10 may further include a speed sensor 64 (e.g., a wheel speed sensor or rotation sensor) configured to measure the speed of the motorcycle 10. The speed sensor 64 may include one or more optical or magnetic sensors, such as one or more Hall effect sensors. The positions of the camera 60, the light sensor 62, and the speed sensor 64 shown in Figure 1 are given as examples, and various positions are possible on the motorcycle 10. For example, in some embodiments, the speed sensor 64 measures the speed of the rear wheel 18 or the speed of the front wheel 14. Also, in some embodiments, the motorcycle 10 includes only the camera 60 or the light sensor 62, and not both. For example, in some embodiments, image data collected via the camera 60 may be used to measure light without requiring a separate light sensor 62. Also, in some embodiments, data described herein as supplied via the camera 60, the light sensor 62, or both may be obtained by the ECU 200 from other sources. Other sources may include, for example, the user's mobile phone, smartwatch, or other wearable, another motorcycle, or other devices that communicate with the motorcycle 10 via one or more communication interfaces.

[0018] As will be explained in more detail with respect to Figures 3 and 4, data from sensors (e.g., camera 60, light sensor 62, speed sensor 64, or a combination thereof) may be used by the ECU 200 as part of the control of the high-beam headlights 42. For example, the ECU 200 may be configured to provide an automatic high-beam (AHB) function. As described above, the AHB function automatically turns off the high-beam headlights in response to the detection of various driving conditions. Such driving conditions may include, for example, driving during the daytime, driving in densely populated areas such as cities (where there is a high probability of other lighting such as streetlights and oncoming and preceding vehicles), driving when oncoming and / or preceding vehicles are detected, driving below a predetermined speed threshold (e.g., 15 to 25 km / h), and driving in fog. Accordingly, the ECU 200 may use data from the light sensor 62, the camera 60, or both to detect whether the motorcycle 10 is being driven during the daytime; use data from the camera 60 to detect whether the motorcycle 10 is being driven in an urban area or other densely populated area (for example, by detecting streetlights, signs, buildings, etc. in the image data); use data from the camera 60 to detect whether the motorcycle 10 is being driven in fog; and use data from the speed sensor 64 to determine whether the vehicle is being driven below a predetermined speed threshold. As described above, in some embodiments, the ECU 200 may obtain data for performing AHB control from other sources or vehicle components, and further from external devices that communicate with the motorcycle 10.For example, the ECU 200 may use the date and time information maintained by the clock of the motorcycle 10 or an external device to determine whether the motorcycle 10 is being operated during the day, may use the objects detected by the cruise control system or the driver assistance system of the motorcycle 10 to determine whether there is an oncoming vehicle and / or a preceding vehicle, or may use the navigation data maintained by the navigation system of the motorcycle 10 or an external device to determine whether the motorcycle 10 is being operated in a densely populated area, and may use the weather information maintained by the infotainment system of the motorcycle 10 or an external device to determine whether the motorcycle 10 is being operated in fog. Therefore, using the sensors described herein to perform AHB control is provided as an exemplary configuration for detecting driving conditions.

[0019] When the vehicle is equipped with an AHB function, the input received from the user to turn on the high beam headlight may be overridden (e.g., ignored) by the AHB function. For example, during daytime driving conditions when the AHB function is enabled, in response to receiving an input (e.g., via the lighting input mechanism 46) to turn on the high beam headlight 42, the AHB function implemented via the ECU 200 prevents the high beam headlight 42 from turning on. Therefore, in such situations (which may be common depending on the type of vehicle, such as a motorcycle), it is necessary to enable the AHB function to turn on the high beam headlight 42. However, when the AHB function is disabled, it prevents the AHB function from operating. This means that ultimately, when the vehicle is being operated under nighttime driving conditions and an oncoming vehicle and / or a preceding vehicle is detected, automatic high beam control is not performed (although the user may rely on such automatic control being performed), and the high beam headlight 42 may affect other vehicles.

[0020] Therefore, to address these and other issues, when enabled, the ECU 200 is configured to provide a daylight override that allows the high beam headlight 42 to be turned on during daytime driving conditions without the need to disable the AHB function even when the AHB function is enabled. Further details regarding the override shall refer to FIGS. 3 and 4.

[0021] FIG. 2 schematically shows the ECU 200 of the motorcycle 10 according to some embodiments. The ECU 200 may include additional components than those illustrated in FIG. 2 and may include components of various configurations. The specific set and configuration of the components illustrated in FIG. 2 are provided as one non-limiting example. Also, the position of the ECU 200 within the motorcycle 10 illustrated in FIG. 1 is provided as an example position. The actual position of the ECU 200 may be different. Also, the functions described herein as being performed via the ECU 200 may be distributed among multiple components of the motorcycle 10, such as between multiple ECUs.

[0022] As shown in FIG. 2, the ECU 200 includes a plurality of electrical and electronic components, which provide power, operation control, and protection to the components and modules within the ECU 200. In some embodiments, as shown in FIG. 2, the ECU 200 includes an electronic processing unit 204 (e.g., an electronic microprocessor, microcontroller, or similar device), a memory 208 (e.g., a non-transitory computer-readable memory), and an input / output (I / O) interface 212. As described above, the ECU 200 may include additional or alternative components, which may include additional electronic processors and memories, or application-specific integrated circuits (ASICs), further, one or more input devices or output devices, or combinations thereof.

[0023] The components of the ECU 200 may be connected in various ways, including, for example, a local bus. The electronic processing unit 204 is communicatively coupled to the memory 208 and executes instructions stored in the memory 208. For example, in some embodiments, the electronic processing unit 204 is configured to retrieve and execute instructions from the memory 208, in particular, those related to the control processes and methods described herein. For example, as shown in Figure 2, the memory 208 may store a daylight override module 210 containing executable instructions that perform the functionality described herein. The instructions described herein and the associated functionality may be combined and distributed in various ways, and in some embodiments, the functionality described herein as being executed via the execution of module 210 may be distributed among fewer or additional modules. Furthermore, the memory 208 may store parameters used by module 210, such as, for example, one or more thresholds, the status of the AHB function of the motorcycle 10 (e.g., a flag or other identifier representing the state), the status of the daylight override of the AHB function (e.g., a flag or other identifier representing the state), or a combination thereof. Furthermore, these parameters may be stored in other memory modules included in the motorcycle 10 that are accessible to the ECU 200. In some embodiments, one or more of these parameters are stored in persistent memory, which allows the parameters (e.g., those set during the previous operation of the motorcycle 10) to be retained and applied (e.g., by default) when the motorcycle 10 is later operated (e.g., powered on).

[0024] The I / O interface 212 enables the ECU 200 to exchange data with other components of the motorcycle 10, the outside of the motorcycle 10, or a combination thereof. For example, the I / O interface 212 may include wired or wireless connections (e.g., wired ports, wireless transceivers, or a combination thereof) that communicate with the vehicle 10's Controller Area Network (CAN) bus, Local Interconnection Network (LIN) bus, or other communication buses or channels. In some embodiments, the I / O interface 212 also includes wired or wireless connections (e.g., wired ports, wireless transceivers, or a combination thereof), and the wired or wireless interface communicates with external devices such as the user's mobile phone, smartwatch, or other wearables via, for example, a short-range wireless connection (e.g., a network using the Bluetooth® communication standard or protocol, a short-range wireless communication link, etc.), a local area network (e.g., a Wi-Fi® connection, etc.). In some embodiments, the I / O interface 212 includes one or more dedicated connections to other components of the motorcycle 10.

[0025] As shown in Figure 2, the ECU 200 may communicate with input mechanisms, such as the lighting input mechanism 46, via the I / O interface 212. Furthermore, the ECU 200 may communicate with the camera 60, the light sensor 62, the wheel rotation sensor 64, or a combination thereof. In some embodiments, communication with the lighting input mechanism 46, the camera 60, the light sensor 62, the wheel rotation sensor 64, or a combination thereof may be performed via the CAN bus of the motorcycle 10. However, in other embodiments, different forms of communication may be used, and one or more intermediate components may process data between the data source and the ECU 200. In some embodiments, the ECU 200 may not communicate with all of the components shown in Figure 2. For example, in some embodiments, if the ECU 200 is configured to perform the override functions described herein, but a separate ECU or component is configured to perform the AHB control described herein, the ECU 200 may not need to receive data from the speed sensor 64, or the camera 60, or a combination thereof.

[0026] As shown in Figure 2, the ECU 200 further communicates with the high-beam headlight 42 (or the high-beam headlight 42, or a control unit associated with the associated headlight assembly) via the I / O interface 212. For example, in some embodiments, the ECU 200 outputs data signals (via the I / O interface 212) that indicate a specific operating state of the high-beam headlight 42, such as whether the high-beam headlight 42 is on or off. For example, the ECU 200 may output (for example, on the CAN bus) a command to turn the high-beam headlight 42 on or off. Alternatively, or in addition to this, the ECU 200 may selectively output or control the power supply to the high-beam headlight 42 (via the I / O interface 212 or another interface) to control whether the high-beam headlight 42 is on or off. In other words, the ECU 200 is configured to generate an output that enables the high-beam headlights 42 to be illuminated, and the output may include data signals or commands, power supplies, or a combination thereof, so that the ECU 200 controls the operation of the high-beam headlights 42. Although not shown in Figure 2, in some embodiments, the ECU 200 may further output one or more data signals to control information provided through one or more user interfaces. To inform the driver (user) of the status of the high-beam headlights 42 (e.g., on or off), the status of the AHB function (e.g., enabled or disabled), the status of the AHB function's daytime running light override (e.g., enabled or disabled), or a combination thereof, for example, the ECU 200 may output one or more data signals to illuminate one or more indicators or display various messages, icons, or other information. In some embodiments, the same data signals output by the ECU 200 to control the high-beam headlights 42 (e.g., those communicated over a CAN bus) are further used by other components within the motorcycle 10 to control the display of information on one or more user interfaces (e.g., without requiring separate data signals from the ECU 200).

[0027] Figure 3 is a flowchart illustrating a method 300 for controlling the high-beam headlights 42 of a motorcycle 10, relating to several embodiments. In this specification, the method 300 is described as being performed by an ECU 200, and more particularly, via a daytime running light override module 210 performed by an electronic processing unit 204 contained within the ECU 200. However, as described above, the functionality described herein may be distributed among multiple modules, devices (processing units, ECUs), or combinations thereof. For example, as described above, parts of the method 300 may be performed via separate ECUs, such as a separate ECU that provides AHB control.

[0028] As shown in Figure 3, method 300 includes receiving an input (for example, via an illumination input mechanism 46 or another type of input mechanism) in block 305 to illuminate the high-beam headlights 42. In some embodiments, the inputs for illuminating the high-beam headlights 42 received in block 305 include an input requesting a static "on" state of the high-beam headlights 42, in contrast to a temporary "flash" state of the high-beam headlights 42. For example, the high-beam headlights 42 may be operated in one or more operating states. One state may include a "flash" or temporary operating state, and another state may include a static "on" state. Different input mechanisms may be provided for these different operating states, or the same input mechanism may be used to specify any of the operating states. For example, in some embodiments, the illumination input mechanism 46 includes a lever. Pressing or moving the lever by a predetermined amount may cause the high-beam headlights 42 to temporarily "flash". The high-beam headlights 42 are turned off in response to the user releasing the lever. Alternatively, the lever may be pressed or moved to another position representing the static "on" state of the high-beam headlight 42, and the lever will be held in that position when the user releases it.

[0029] The temporary “flash” operating mode may be used to send signals to other vehicles (for example, to alert other drivers of an intention to change lanes or to use hazard lights), so the ECU 200 may be configured to enable the operation of the high-beam headlights 42 in “flash” mode (in block 315 of Figure 3), regardless of whether the automatic high beam (ABH) function is enabled or disabled. However, in other embodiments, the ECU 200 may process any type of input to illuminate the high-beam headlights 42, as shown in blocks 305 to 330 of Figure 3.

[0030] As shown in Figure 3, after receiving an input (in block 305) for turning on the high-beam headlights 42, the ECU 200 determines (in block 310) whether the AHB function of the motorcycle 10 is enabled. In some embodiments, memory 208 may store the status of the AHB function (e.g., a status flag or other identifier), which may be set by the user via one or more user interfaces provided by the motorcycle 10. Also in some embodiments, a mobile phone, smartwatch, other wearable, key fob, or other device may provide one or more user interfaces for setting the status of the AHB function (e.g., enabled or disabled), and this setting may be communicated to the motorcycle 10 and the ECU 200. Furthermore, in some embodiments, the status of the AHB function may be stored or managed by a separate component (e.g., a separate ECU) included in the motorcycle 10.

[0031] In response to detecting that the ABH function is disabled (proceeding to the "No-Disabled" path in block 310), the ECU 200 enables the high-beam headlights 42 to illuminate (in block 315). As described above, the ECU 200 may be configured to output one or more data signals instructing the high-beam headlights 42 (or associated controller or ECU) to illuminate the high-beam headlights 42. Furthermore, various user interfaces of the motorcycle 10 may be modified to notify the user that the high-beam headlights 42 have been illuminated.

[0032] In response to detecting that the ABH function is enabled (proceeding to the "Yes - Enabled" path in block 310), the ECU 200 determines the current time of day and uses this time to determine whether the motorcycle 10 is operating during the daytime (in block 320). The ECU 200 may determine the current time based on data received from, for example, the camera 60, the light sensor 62, or a combination thereof. For example, in response to a data signal from the light sensor 62 indicating that the detected light level satisfies a predetermined light threshold (e.g., 1000 lux) (e.g., is 1000 lux or greater), the ECU 200 may set the current time to "daytime". Alternatively, in response to a data signal from the light sensor 62 indicating that the detected light level does not satisfy a predetermined light threshold (e.g., is below the light threshold), the ECU 200 may set the current time to "nighttime". In some embodiments, the ECU 200 may similarly compare the light level determined based on image data collected via the camera 60 with a predetermined threshold to determine whether the current time is daytime or nighttime. Any threshold used by the ECU 200 as part of determining the current time may be stored in the memory 208. Also in some embodiments, other components in the motorcycle 10 may track the current time, and the ECU 200 may use such information to determine the current time (for example, it may not be necessary for the ECU 200 to perform a comparison with a threshold, receive data from the light sensor 62 or camera 60, or a combination thereof). Alternatively, or in addition to the above, the ECU 200 may use the current time (and optionally the current date) maintained by the motorcycle 10's clock to determine whether the motorcycle 10 is operating during the daytime or at night.

[0033] In response to determining that the current time is daytime (proceeding to the "Yes" path in block 320), the ECU 200 determines whether the daytime running light override for the AHB function is enabled (in block 325). Similar to the status of the AHB function, the status of the daytime running light override (e.g., a status flag or other identifier) ​​may be stored in memory 208 and set by the user via one or more user interfaces provided by the motorcycle 10. In some embodiments, a mobile phone, smartwatch or other wearable, key fob or other device may provide one or more user interfaces for setting the status of the daytime running light override (e.g., enabled or disabled), and this setting may be communicated to the motorcycle 10 and the ECU 200. Furthermore, in some embodiments, the status of the daytime running light override may be stored or managed by a separate component (such as an ECU) included in the motorcycle 10.

[0034] When the daytime running light override is enabled (proceeding to the "Yes - Enabled" path in block 325) and in response that the current time is daytime (proceeding to the "Yes" path in block 320), the ECU 200 enables the high-beam headlights 42 to be turned on (in block 315). As described above, the ECU 200 may be configured to output one or more data signals to the high-beam headlights 42 (or the controller or ECU associated therewith) instructing them to turn on the high-beam headlights 42. In addition, various user interfaces of the motorcycle 10 may be modified to inform the user that the high-beam headlights 42 have been turned on. For example, an indicator associated with the high-beam headlights 42 may be illuminated, and in some embodiments, indicators associated with the daytime running light override, the AHB function, or both may be modified. In some embodiments, to avoid user confusion, the indicator for the AHB function may be turned off when the daytime running light override is in effect (and automatically returned to illuminate when the override is no longer in effect). However, in some cases, the AHB function is not actually disabled in this situation, so this change may be for informational purposes only.

[0035] In particular, illuminating the high-beam headlights 42 in this situation may not affect the current status of the AHB function. In other words, the high-beam headlights 42 are activated in this situation while maintaining the AHB function in an enabled state (i.e., without disabling the AHB function). Thus, the high-beam headlights 42 may remain illuminated in this situation until an additional input is received to turn off the high-beam headlights 42, or until the motorcycle 10 is no longer driven during the daytime (as is done via the AHB function). When it is detected that the motorcycle 10 is no longer driven during the daytime, the daytime light override becomes inapplicable and the AHB control is applied (because the AHB function is not disabled and remains enabled). In this way, while maintaining the AHB function in an enabled state, the daytime light override allows the motorcycle 10's high-beam headlights 42 to be selectively illuminated during daytime driving conditions, thereby allowing the AHB control to be applied when daytime driving conditions are no longer detected. In other words, the daytime running light override blocks the automatic control of the high-beam headlights via the AHB function while the current time is daytime, without disabling the AHB function. In particular, while the high-beam headlights 42 are illuminated, method 300 may be repeated (for example, starting from block 310) to continue checking for changes in driving conditions and controlling the high-beam headlights 42 in response.

[0036] As shown in Figure 3, in response to the daytime running light override being disabled (proceeding to the "No - Disabled" path in block 325) and the current time being daytime (proceeding to the "Yes" path in block 320), the ECU 200 executes the AHB function and prevents the high-beam headlights 42 from turning on in response to the received input (in block 330) (i.e., the high-beam headlights 42 remain off). Furthermore, in several embodiments, various user interfaces of the motorcycle 10 may be modified to inform the user that the high-beam headlights 42 are not yet on. For example, an indicator may be provided in the user interface to inform the user that the AHB function is enabled or active. In several embodiments, this indicator may be temporarily modified, such as flashing, to inform the user that the user input to turn on the high-beam headlights 42 has been overridden due to the active state of the AHB function.

[0037] Similarly, as shown in Figure 3, in response to the current time not being daytime (proceeding to the "No" path in block 320), the ECU 200 continues to perform the AHB function and checks for other driving conditions that can prevent the high-beam headlights 42 from turning on. The various conditions checked as part of the AHB function may vary, but Figure 3 shows an example set of such conditions. This may include determining whether the motorcycle 10 is driving in an urban area or other densely populated area (in block 335), whether traffic (e.g., oncoming vehicles detected via the headlights and / or preceding vehicles detected via the taillights) has been detected (in block 340), whether the motorcycle 10 is driving below a predetermined speed threshold (in block 345), and whether the motorcycle 10 is driving in fog (in block 350). As described above, these driving conditions may be detected using various data from vehicle sensors communicating with the ECU 200, external devices or systems communicating with the ECU 200, or a combination thereof. In response to the detection of any one of these conditions, the ECU 200 executes the AHB function and prevents the high-beam headlights 42 from illuminating in response to the received input (in block 330). As described above, in some aspects, various user interfaces of the motorcycle 10 may be modified to notify the user that the high-beam headlights 42 are not illuminated. Thresholds, rules, or logic applied as part of the AHB function may be set to differ depending on the jurisdiction and / or the type of vehicle or terrain. In some aspects, it may depend on applicable rules, such as UN Economic Commission for Europe (UN / ECE) Rule 48.

[0038] As shown in Figure 3, in response to the absence of any detected conditions, the ECU 200 illuminates the high-beam headlights 42 in response to the received input (in block 315). As described above, various user interfaces of the motorcycle 10 may be modified to notify the user that the high-beam headlights 42 have been illuminated.

[0039] In some embodiments, one or more additional checks may be included as part of Method 300. Furthermore, in some embodiments, as shown in Figure 4, for example, Method 300 may include determining the market configuration of the motorcycle 10 and determining whether the market configuration allows the implementation of the daytime running light override (in block 360) before implementing the daytime running light override. In some jurisdictions, such as different geographical jurisdictions, certain overrides of the AHB function may not be enabled. In such scenarios, Method 300 may be configured to check the market configuration of the motorcycle 10, i.e., a market configuration that can be stored in memory 208 or another memory module of the motorcycle 10 and can be set at time of manufacture or sale, or can be set dynamically, such as based on the current geographical location of the motorcycle, and to compare the market configuration of the motorcycle 10 with a list of market configurations that are allowed to be overridden, or conversely, a list of market configurations that are not allowed to be overridden (similarly stored in memory 208 or accessed by the ECU 200). As shown in Figure 4, in response to the market configuration of motorcycle 10 being a market configuration that allows daytime running light override (proceeding to the "Allow" path in block 360), ECU 200 allows the high-beam headlights 42 to be illuminated as described above (in block 315). Alternatively, in response to the market configuration of motorcycle 10 not being a market configuration that allows daytime running light override (proceeding to the "Do Not Allow" path in block 360), ECU 200 performs the AHB function and prevents the high-beam headlights 42 from being illuminated in response to the received input as described above (in block 330).

[0040] Accordingly, the embodiments described herein provide a method and system for providing a daytime running light override for the AHB function, which allows the high-beam headlights to be illuminated during daytime driving conditions without disabling the AHB function, which may otherwise affect the future operation of the high-beam headlights (e.g., identification and automatic control of the high-beam headlights under other driving conditions), even when the AHB function is enabled.

[0041] Various features and advantages of several embodiments are described in the following claims.

Claims

1. The high-beam headlights installed on the vehicle, The sensors mounted on the aforementioned vehicle, It is an electronic control unit, The high-beam headlights are configured to receive an input, It is configured to determine the status of the automatic high beam function of the vehicle, It is configured to determine the override status of the automatic high beam function of the vehicle, It is configured to determine the current time based on the data received from the aforementioned sensor, The system includes an electronic control unit configured to override the automatic high beam function in response to the status of the automatic high beam function being enabled, the current time being daytime, and the status of the override being enabled, thereby enabling the high beam headlights to be turned on based on the input while maintaining the status of the automatic high beam function in an enabled state. system.

2. Furthermore, the system according to claim 1, wherein the electronic control unit is configured to prevent the automatic high beam function from turning on the high beam headlights based on the input in response to the current time being daytime and the status of the override being disabled.

3. The system according to claim 1, wherein the sensor includes at least one of a camera and a light sensor.

4. The system according to claim 1, wherein the electronic control unit is further configured to receive a second input and to set the status of the override based on the second input.

5. The system according to claim 4, further comprising a user interface mounted on the vehicle, wherein the electronic control unit is configured to receive the second input from the user interface.

6. The aforementioned electronic control unit is further configured to determine the market configuration of the vehicle, The system according to claim 1, in response to the current time being daytime, the status of the override being enabled, and the override being enabled in the market configuration, the electronic control unit is configured to override the automatic high beam function to enable the high beam headlights based on the input, while maintaining the status of the automatic high beam function in an enabled state.

7. A method for controlling the high-beam headlights of a vehicle, The electronic control unit of the vehicle includes the step of receiving an input in order to turn on the high beam headlights, The steps include determining the status of the vehicle's automatic high beam function using the vehicle's electronic control unit, The electronic control unit determines the status of the override of the vehicle's automatic high beam function, The electronic control unit includes the step of determining the current time, A method comprising the steps of enabling the electronic control unit to override the automatic high beam function and turn on the high beam headlights based on the input, in response to the status of the automatic high beam function being enabled, the current time being daytime, and the status of the override being enabled, while maintaining the status of the automatic high beam function in an enabled state.

8. The method according to claim 7, further comprising the step of enabling the high-beam headlights to be turned on based on the input in response to the current time being nighttime.

9. The method according to claim 7, further comprising the step of preventing the automatic high beam function from turning on the high beam headlights based on the input in response to the current time being daytime and the status of the override being disabled.

10. The method according to claim 7, further comprising the step of enabling the high beam headlights to be illuminated based on the input in response to the status of the automatic high beam function being disabled.

11. The method according to claim 7, wherein the step of determining the current time includes determining the current time based on data received from at least one of a camera mounted on the vehicle and an optical sensor mounted on the vehicle.

12. moreover, A step of receiving a second input, The method according to claim 7, further comprising the step of setting the status of the override based on the second input.

13. The method according to claim 12, wherein the step of receiving the second input includes receiving the second input via the user interface of the vehicle.

14. Furthermore, the step includes determining the market configuration of the vehicle, The method according to claim 7, wherein overriding the automatic high beam function in order to enable the high beam headlights based on the input while maintaining the status of the automatic high beam function in an enabled state includes overriding the automatic high beam function in response to the current time being daytime, the status of the override being enabled, and the override being enabled in the market configuration.

15. A computer program that includes instructions for performing a series of functions when executed by one or more electronic processors, wherein the series of functions are: To illuminate the vehicle's high-beam headlights, it receives an input, To determine the status of the automatic high beam function of the aforementioned vehicle, To determine the override status of the automatic high beam function of the vehicle, Determining the current time, A computer program comprising: enabling the automatic high beam function to override the automatic high beam function in response to the status of the automatic high beam function being enabled, the current time being daytime, and the status of the override being enabled, and enabling the high beam headlights based on the input while maintaining the status of the automatic high beam function in an enabled state.

16. The computer program according to claim 15, further comprising the following: the set of functions further includes preventing the automatic high beam function from turning on the high beam headlights based on the input in response to the current time being daytime and the status of the override being disabled.

17. The aforementioned series of functions further, Accepting a second input, The computer program according to claim 15, further comprising setting the status of the override based on the second input.

18. The computer program according to claim 17, wherein receiving the second input includes receiving the second input via a user interface mounted on the vehicle.

19. The aforementioned series of functions further include determining the market configuration of the vehicle, The computer program of claim 15, which overrides the automatic high beam function to enable the high beam headlights based on the input, while maintaining the status of the automatic high beam function in an enabled state, is performed in response to the current time being daytime, the status of the override being enabled, and the override being enabled in the market configuration.

20. The computer program according to claim 15, further comprising the set of functions to block the automatic control of the high-beam headlights via the automatic high-beam function while the current time is daytime, with the high-beam headlights illuminated in response to the status of the override being enabled.

Images