Central high-mount stop lamp system
Through the wireless auxiliary CHMSL system, the auxiliary light is activated or deactivated by sensor data, which solves the problem of CHMSL failure caused by cargo occlusion, ensuring that the rear of the vehicle is always visible, and improving safety.
Patent Information
- Application Number
- CN202410637084.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2023-05-23
- Filing Date
- 2024-05-22
- Publication Date
- 2024-11-26
AI Technical Summary
The existing vehicle central high-level brake lights (CHMSL) are easily blocked when loading goods, resulting in loss of protection. Especially when the cargo table position changes, it is difficult to effectively activate or maintain the visibility of the brake lights.
The wireless auxiliary CHMSL system is adopted, including sensors, main CHMSL, wireless auxiliary CHMSL, vehicle wireless transceiver and processor, to activate or deactivate wireless auxiliary CHMSL through sensor data to ensure that a significant deceleration signal can still be provided under cargo occlusion.
The wireless assisted CHMSL system simplifies installation and is integrated into other lighting components of the vehicle to ensure that it can still be activated effectively when the cargo is blocked, providing obvious deceleration signals, and improving rear safety of the vehicle.
Smart Images

Figure CN119018047A_ABST
Abstract
Description
[0001] introduction
[0002] The present disclosure relates to vehicles. More particularly, the present disclosure relates to a center high mounted stop lamp (CHMSL) for a vehicle. Summary of the invention
[0003] Embodiments of the present disclosure advantageously provide a center high mounted stop light (CHMSL) system for a vehicle. In many embodiments, the CHMSL system includes a sensor, a main CHMSL, a wireless auxiliary CHMSL, a vehicle wireless transceiver, and at least one processor coupled to the sensor, the main CHMSL, and the vehicle wireless transceiver. The sensor is configured to generate sensor data. The main CHMSL includes a main light. The wireless auxiliary CHMSL includes an auxiliary light, a battery, and a control circuit, the control circuit including a CHMSL wireless transceiver and a microcontroller. The processor is configured to facilitate activation of the wireless auxiliary CHMSL based on the sensor data. BRIEF DESCRIPTION OF THE DRAWINGS
[0004] Figure 1A A diagram of an exemplary vehicle is depicted in accordance with an embodiment of the present disclosure.
[0005] Figure 1B Depicted is a diagram of an exemplary vehicle having a cargo box according to an embodiment of the present disclosure.
[0006] Figure 1C A diagram of an exemplary vehicle with a cargo box and a wireless auxiliary CHMSL is depicted according to an embodiment of the present disclosure.
[0007] Figure 2A A diagram of an exemplary vehicle with a short cargo is depicted in accordance with an embodiment of the present disclosure.
[0008] Figure 2B A diagram of an exemplary vehicle with high cargo and wireless assisted CHMSL is depicted according to an embodiment of the present disclosure.
[0009] Figure 3 A block diagram of exemplary components of a wireless assisted CHMSL according to an embodiment of the present disclosure is presented.
[0010] FIG. 4A to FIG. 4D Several views of an exemplary wireless-assisted CHMSL are depicted, according to embodiments of the present disclosure.
[0011] Figure 4E and Figure 4F Depicted is a perspective view of an exemplary wirelessly assisted CHMSL mounted to a cargo bed rail in accordance with an embodiment of the present disclosure.
[0012] Figure 5A block diagram of exemplary components of an exemplary vehicle according to an embodiment of the present disclosure is presented.
[0013] Figure 6 A sequence diagram of a CHMSL system for a vehicle according to an embodiment of the present disclosure is presented. DETAILED DESCRIPTION
[0014] The present disclosure generally relates to features for a center high mounted stop light (CHMSL) system. Other terms for CHMSL include center brake light, high mounted or eye level brake light, cyclops brake light, safety brake light, etc. The purpose of a CHMSL is to protect a car or light truck from being struck from behind by another vehicle. When the brakes are applied, the CHMSL sends an obvious and unambiguous message to the driver of the following vehicle that they must slow down.
[0015] When the CHMSL is mounted on top of a pickup truck cab, cargo loaded in or on the cargo bed may obstruct the CHMSL, defeating this added protection. Similarly, a cover or camper installed in the cargo bed may obstruct the CHMSL. When the CHMSL is mounted on a tailgate, when the vehicle is driven with the tailgate in the lowered position, the CHMSL will face the ground, also defeating this added protection.
[0016] Embodiments of the present disclosure advantageously provide a CHMSL system for a vehicle. In many embodiments, the CHMSL system includes a sensor, a main CHMSL, a wireless auxiliary CHMSL, a vehicle wireless transceiver, and at least one processor coupled to the sensor, the main CHMSL, and the vehicle wireless transceiver. The sensor is configured to generate sensor data. The main CHMSL includes a main light. The wireless auxiliary CHMSL includes an auxiliary light, a battery, and a control circuit, the control circuit including a CHMSL wireless transceiver and a microcontroller. The processor is configured to facilitate activation of the wireless auxiliary CHMSL based on the sensor data. In certain embodiments, the processor is also configured to facilitate deactivation of the main CHMSL based on the sensor data.
[0017] The wireless auxiliary CHMSL is easy to install, eliminates the complexity of the backup CHMSL wired solution, and integrates with other exterior lighting elements on the vehicle.
[0018] Figure 1A A diagram of a vehicle 100 is depicted in accordance with an embodiment of the present disclosure.
[0019] The vehicle 100 includes, among other things, a body, a propulsion system, backup or accessory systems, etc. In many embodiments, the body 110 includes, among other things, a frame or chassis, a front end 112, a driver / passenger compartment or cockpit 113, a main CHMSL 114, taillights 115, a rear-facing camera 116, a cargo bed 118, a rear end 120, etc. In general, the vehicle 100 is any vehicle that includes a cargo bed, such as a pickup truck, a flatbed truck, a dump truck, etc.
[0020] The propulsion system may be a conventional propulsion system including an internal combustion engine and a transmission system, an electric propulsion system including an electric motor and an energy storage subsystem (such as a battery), or a hybrid propulsion system that combines an internal combustion engine and a transmission system with an electric propulsion system. The internal combustion engine may be powered by gasoline fuel, diesel fuel, natural gas, methanol, ethanol, biodiesel, etc. In many hybrid propulsion systems, the internal combustion engine and the electric propulsion system provide power to the wheels at the same time or at different times. In some hybrid propulsion systems, the internal combustion engine may be coupled to a generator instead of a transmission system, and the electric motor of the electric propulsion system always provides power to the wheels.
[0021] In many embodiments, the vehicle 100 has an electric propulsion system that includes, among other things, one or more electronic control units (ECUs), one, two, or four (or more) electric motors 130 with associated drivetrains, wheels 132, an energy storage subsystem, a suspension subsystem, a steering subsystem, etc. The energy storage subsystem may include, among other things, one or more ECUs, a battery pack 140, a vehicle charging subsystem including a charging port, etc. In other embodiments, the vehicle 100 includes a conventional propulsion system or a hybrid propulsion system.
[0022] Backup or auxiliary systems include, among others, one or more ECUs, power distribution systems, heating and air conditioning systems, cockpit displays, interior and exterior lighting systems, integrated electrical equipment, and the like.
[0023] Figure 1B A diagram of a vehicle 100 with tall cargo 10 is depicted according to an embodiment of the present disclosure.
[0024] In many embodiments, tall cargo 10 is secured to removable cargo bed rails 119F (front) and removable cargo bed rails 119R (rear) during transport. Typically, at least two removable cargo bed rails 119 are required to support tall cargo 10 above cargo bed 118. Figure 1BAs shown in FIG, the tall cargo 10 obscures the main CHMSL 114 from view by vehicles, motorcycles, semi-trailers, etc., following the vehicle 100. Obstructing the view of the main CHMSL 114 may cause safety-related issues for these drivers, riders, and operators. In some other embodiments, a removable cargo bed rail 119 is not provided, and if desired, the tall cargo 10 may be loaded directly into the cargo bed 118 and secured therein using ropes, straps, etc.
[0025] When a tall cargo 10 is secured to a removable cargo bed rail 119 or simply loaded into a cargo bed 118, the tall cargo 10 may partially or completely obstruct the field of view of the rearward-pointing camera 116. In many embodiments, image data from the rearward-pointing camera 116 may be used to determine whether the primary CHMSL 114 is obstructed by a tall cargo 10, such as with respect to FIG. Figure 5 and Figure 6 In some other embodiments, sensor data from one or more other sensors (such as other cameras, proximity sensors located in or near the cargo bed 118, etc.) can be used to determine whether the main CHMSL 114 is blocked by the tall cargo 10. The proximity sensor data can be used alone or in conjunction with the camera image data to determine whether the main CHMSL 114 is blocked by the tall cargo 10, as described in detail in relation to FIG. Figure 5 and Figure 6 discussed.
[0026] Figure 1C A diagram of a vehicle 100 with a tall cargo 10 and a wireless assisted CHMSL 200 is depicted, according to an embodiment of the present disclosure.
[0027] In many embodiments, the wireless auxiliary CHMSL 200 can be temporarily or removably attached or mounted to the removable cargo bed rail 119R, as described with respect to Figure 4E and Figure 4F In some other embodiments, the wireless assisted CHMSL 200 may be incorporated as an integrated component within the removable cargo bed rail 119R. In certain embodiments, the wireless assisted CHMSL 200 may include lateral extensions that attach to the cargo bed rail mounting locations so that when tall cargo is loaded directly into the cargo bed 118, it is not necessary to use the removable cargo bed rail 119R for support.
[0028] like Figure 1C As shown in FIG. 1 , although the tall cargo 10 blocks the main CHMSL 114 from being observed, the tall cargo 10 does not block the wireless auxiliary CHMSL 200 from being observed by the vehicle, motorcycle, semi-trailer, etc. following the vehicle 100 .
[0029] Figure 2AA diagram of a vehicle 100 with a short cargo 20 is depicted according to an embodiment of the present disclosure.
[0030] like Figure 2A As shown in FIG. 1 , the short cargo 20 does not obstruct the main CHMSL 114 from being viewed by vehicles, motorcycles, semi-trailers, etc. following the vehicle 100 .
[0031] Figure 2B A diagram of a vehicle 100 with a tall cargo 30 and a wireless assisted CHMSL 200 is depicted, according to an embodiment of the present disclosure.
[0032] Tall cargo 30 is loaded directly into the cargo bed 118, and a removable cargo bed track 119R is provided as a convenient mounting location for the wireless auxiliary CHMSL 200. Figure 2B As shown in FIG. 1 , although the tall cargo 30 blocks the main CHMSL 114 from being observed, the tall cargo 30 does not block the wireless auxiliary CHMSL 200 from being observed by the vehicle, motorcycle, semi-trailer, etc. following the vehicle 100 .
[0033] Figure 3 A block diagram of exemplary components of a wireless assisted CHMSL 200 is presented in accordance with an embodiment of the present disclosure.
[0034] In many embodiments, the wireless auxiliary CHMSL 200 includes, among other things, a housing 210, an auxiliary light 220, a control circuit 230, one or more rechargeable batteries 240, and a charging port 250. The control circuit 230 includes, among other things, a battery sensor 231, a battery charger 232, an auxiliary light driving circuit 233, a microcontroller unit (MCU) 234, and an antenna 238.
[0035] The charging port 250 is coupled to the battery charger 232 and receives a cable (such as a USB-C cable) for connecting to a 5V power source (such as a 110V AC-5VDC power supply or power brick). In many embodiments, the MCU 234 can be coupled to certain connector pins (such as USB UART TX and RX pins) within the charging port 250, and the USB-C cable can couple the charging port 250 to a computer system that communicates with the MCU 234 for various purposes.
[0036] The battery sensor 231 is coupled to the battery charger 232, the MCU 234, and the rechargeable battery 240. The battery sensor 231 is configured to sense the charge level of the rechargeable battery 240 and generate and transmit one or more battery charging signals to the MCU 234. The battery sensor 231 may also be configured to receive certain signals from the MCU 234.
[0037] The battery charger 232 is coupled to the battery sensor 231, the auxiliary light driving circuit 233, the MCU 234, the charging port 250, and the power button 270. During normal operation, the battery charger 232 is configured to supply power from the rechargeable battery 240 (through the battery sensor 231) to the auxiliary light driving circuit 233 and the MCU 234. In other words, during normal operation, the rechargeable battery 240 is coupled to the control circuit 230 and is configured to supply power to the auxiliary light 220 and the control circuit 230.
[0038] During battery charging, the cable connects the 5V power supply to the charging port 250, and the battery charger 232 is configured to provide a charging voltage and a charging current to the rechargeable battery 240 through the battery sensor 231. The battery charger 232 is also configured to generate and transmit one or more status signals to the MCU 234, and receive a battery charging enable signal from the MCU 234. The battery charger 232 supplies power (or not supplies power) to the auxiliary light driving circuit 233 and the MCU 234 based on the state of the power button 270.
[0039] In many embodiments, two rechargeable batteries 240 are connected in parallel, such as two LiFePO418650 rechargeable batteries, each rechargeable battery produces a nominal voltage of 3.2V and has a capacity of 2000mAh (6.4Wh). In many embodiments, the driver cannot access the rechargeable batteries 240. In some embodiments, the rechargeable batteries 240 can be accessed (and replaced) through a waterproof battery compartment cover in the housing 210.
[0040] The auxiliary light driver circuit 233 is coupled to the battery charger 232 and the auxiliary light 220. The auxiliary light driver circuit 233 is configured to provide power to the auxiliary light 220, generate and transmit a light power status signal to the MCU 234, and receive a light enable signal from the MCU 234. In many embodiments, the auxiliary light 220 is an LED light strip having a plurality of light emitting diodes (LEDs), and the auxiliary light driver circuit 233 is an LED driver circuit that increases or boosts the voltage provided by the battery charger 232. The LED light strip may include red LEDs, or may include white LEDs with a red lens or a red translucent cover. Other lamp technologies may also be used.
[0041] MCU 234 typically includes, among other things, a microcontroller having a processor 235 (such as a central processing unit or CPU, etc.) and memory 236 (such as flash memory, ROM, RAM, SRAM, etc.), and a wireless transceiver 237 connected to an antenna 238. In many embodiments, processor 235 can be an Arm Cortex CPU, etc.
[0042] Typically, the wireless transceiver 237 is configured to transmit messages to the vehicle 100 via a wireless communication link, and receive messages from the vehicle 100 via a wireless communication link. In some embodiments, the wireless transceiver 237 is a Bluetooth 2.4 GHz RF transceiver, the MCU 234 is connected to the Bluetooth pairing button 260, and the wireless communication link is a Bluetooth low energy (BLE) link. In some other embodiments, the wireless transceiver 237 is configured to support one or more IEEE 802.11 wireless communication standards (such as 802.11A, B, G, N and AC), and the wireless communication link is a WiFi link.
[0043] Typically, the MCU 234 is configured to turn on the auxiliary lights 220 in response to receiving an activation message transmitted via a wireless communication link from a wireless transceiver connected to the control system of the vehicle 100, and to turn off the auxiliary lights 220 in response to receiving a deactivation message transmitted via a wireless communication link from a wireless transceiver connected to the control system of the vehicle 100.
[0044] The MCU 234 may also be configured to generate a battery charge enable signal based on the battery charge signal from the battery sensor 231 and the status signal from the battery charger 232, and transmit the battery charge enable signal to the battery charger 232. In response to receiving the battery charge enable signal from the MCU 234, the battery charger 232 may be configured to charge the rechargeable battery 240.
[0045] MCU 234 may also be configured to determine a battery charge level based on the battery charge signal and generate a status message including the battery charge level for transmission to vehicle 100 via wireless transceiver 237 .
[0046] The MCU 234 can also be configured to determine the fault status of the rechargeable battery 240 based on the battery charging signal from the battery sensor 231, determine the fault status of the auxiliary light 220 based on the lamp power status signal from the auxiliary light driving circuit 233, determine the fault status of the processor 235 and the fault status of the wireless transceiver 237, and generate a status message including the fault status for transmission to the vehicle 100 via the wireless transceiver 237.
[0047] In certain embodiments, MCU 234 is a Bluetooth Low Energy (BLE) wireless MCU.
[0048] FIG. 4A to FIG. 4D Several views of a wirelessly assisted CHMSL 200 are shown according to an embodiment of the present disclosure.
[0049] Figure 4A A front view of a wireless assisted CHMSL 200 according to an embodiment of the present disclosure is depicted. More specifically, Figure 4A A housing 210 and an auxiliary light 220 are depicted.
[0050] Figure 4B A rear view of a wireless assisted CHMSL 200 according to an embodiment of the present disclosure is depicted. More specifically, Figure 4B Depicted are housing 210 and mounting arm 212. Mounting arm 212 engages a portion of removable cargo bed rail 119R to attach wireless assisted CHMSL 200 to removable cargo bed rail 119R.
[0051] Figure 4C A top view of a wireless assisted CHMSL 200 is depicted according to an embodiment of the present disclosure. More specifically, Figure 4C Housing 210 and mounting arm 212 are depicted.
[0052] Figure 4D A bottom view of a wireless assisted CHMSL 200 according to an embodiment of the present disclosure is depicted. More specifically, Figure 4D Housing 210 , mounting arm 212 , Bluetooth pairing button 260 , and power button 270 are depicted.
[0053] Figure 4E and Figure 4F Depicted are top and bottom perspective views, respectively, of a wirelessly assisted CHMSL 200 mounted to a removable cargo bed rail 119R, in accordance with an embodiment of the present disclosure.
[0054] More specifically, Figure 4E and Figure 4F The housing 210, mounting arms 212, auxiliary lights 220, and the removable cargo bed rail 119R are depicted. In many embodiments, each mounting arm 212 includes a top mounting arm portion 212T that engages with a transverse channel 119C in a top portion of the removable cargo bed rail 119R and a bottom mounting arm portion 212B that engages with a smooth surface 119S of a bottom portion of the removable cargo bed rail 119R.
[0055] The top mounting arm portion 212T is attached to or forms part of the housing 210, and the bottom mounting arm portion 212B is removably attached to a corresponding top mounting arm portion 212T. Each bottom mounting arm portion 212B is secured to a corresponding top mounting arm portion 212T using a fastener 214 (such as a bolt, screw, etc.) that secures the wireless auxiliary CHMSL 200 to the removable cargo bed rail 119R.
[0056] Figure 5 A block diagram 500 of exemplary components of vehicle 100 is presented, according to an embodiment of the present disclosure.
[0057] Typically, the vehicle 100 includes a control system 520 that is configured to perform the functions necessary to operate the vehicle 100. In many embodiments, the control system 520 includes a plurality of electronic control units (ECUs) 530 coupled to an ECU bus 522 (also referred to as a controller area network or CAN). Each ECU 540 performs a specific set of functions and includes, among other things, a microprocessor 542 coupled to a memory 544 and an ECU bus I / F 546. In certain embodiments, the control system 520 may include one or more systems on a chip (SOCs). Each SOC may include multiple multi-core processors coupled to a high-speed interconnect and on-chip memory, and may perform a much larger set of functions than a single ECU 540.
[0058] The control system 520 is coupled to sensors, input / output (I / O) devices, position lights (such as tail lights 115 and main CHMSL 114), actuators (such as brake pedal 121), and other components within the propulsion system, energy storage system, and auxiliary systems. The sensors may include, for example, cameras (such as rear-facing camera 116), proximity sensors 117, other sensors or systems, etc. The proximity sensor 117 may include a radar sensor, an ultrasonic sensor, an optical sensor such as a photoelectric sensor, a photocell, a laser rangefinder, etc. The I / O devices may include, for example, a user interface, a front display 122, a rear display, etc. In addition, the control system 520 may be coupled to one or more networks, such as a WiFi network 540, etc.
[0059] In certain embodiments, one or more ECUs 530 may include necessary interfaces to directly couple to specific sensors, I / O devices, actuators, and other vehicle system components. For example, the body control module (BCM) ECU 528 may be directly connected to the taillights 115 and the main CHMSL 114 via a wired communication link, the vehicle dynamics module (VDM) ECU 530 may be directly connected to the brake pedal 121 via a wired communication link, and the experience management module (XMM) ECU 532 may be directly connected to the front display 122 via a wired communication link such as HDMI.
[0060] The control system 520 may include a central gateway module (CGM) ECU 524 that provides a central communication hub for the vehicle 100. The CGM ECU 524 includes (or is coupled to) an I / O interface 523 to receive data from sensors, I / O devices, actuators, and other vehicle system components and to send commands to sensors, I / O devices, actuators, and other vehicle system components, etc. The CGM ECU 524 also includes (or is coupled to) a network interface 525 that provides network connectivity via an ECU bus (or CAN), a local interconnect network (LIN) port, an Ethernet port, etc.
[0061] For example, the CGM ECU 524 may receive data from the rear-facing camera 116, the proximity sensor 117, other sensors or systems, etc., and the user interface, and then transmit the data to the appropriate ECU 540 via the ECU bus 522. Similarly, the CGM ECU 524 may receive commands and data from the ECU 530 and send them to the appropriate I / O devices, actuators, and vehicle components. For example, a command to display a GUI widget may be received from one or more ECUs 530 and sent to the XMM EDU 532 for display on the front display 122, etc. The GUI widget may indicate that the main CHMSL 114 is blocked and / or has been deactivated, that the wireless auxiliary CHMSL 200 has been activated (and turned on) based on a brake engagement signal received by the VDM ECU 530, and that the wireless auxiliary CHMSL 200 has been turned off based on a brake disengagement signal received by the VDM ECU 530, etc.
[0062] In addition, the CGM ECU 524 may also function as a master control for different vehicle modes (eg, road driving mode, parking mode, off-road mode, towing mode, camping mode), thereby controlling certain vehicle components associated with placing the vehicle in one of these vehicle modes.
[0063] The control system 520 may include a telematics control module (TCM) ECU 526 that provides a vehicle communication gateway for the vehicle 100. The TCM ECU 526 includes (or is coupled to) a network interface 527 that provides network connectivity to support functions such as over-the-air (OTA) software updates, communication between the vehicle and the Internet, communication between the vehicle and a computing device, onboard navigation, vehicle-to-vehicle communication, communication between the vehicle and landscape features (e.g., automatic toll road sensors, automatic toll booths, power distributors at charging stations), automatic call functions, etc.
[0064] In certain embodiments, the wireless transceiver 237 is an IEEE 802.11 (WiFi) transceiver, the network interface 527 is an IEEE 802.11 (WiFi) transceiver, and the TCM ECU 526 communicates with the wireless auxiliary CHMSL 200 via an IEEE 802.11 (WiFi) wireless communication link. In other words, the network interface 527 is a vehicle wireless transceiver that establishes a wireless communication link with the wireless auxiliary CHMSL 200.
[0065] The control system 520 may include a vehicle access system (VAS) ECU 534. In many embodiments, the wireless transceiver 237 is a Bluetooth transceiver, the VAS EDU 534 includes (or is coupled to) a Bluetooth interface 535, and the VAS EDU 534 communicates with the wireless auxiliary CHMSL 200 via a Bluetooth wireless communication link.
[0066] In many embodiments, the control system 520 may also include one or more image data processing (IDP) ECUs that process image data received from the rear-facing camera 116 (and other cameras) and send the processed image data to the front display 122. The IP ECU may also be configured to execute an object detection algorithm to determine if the primary CHMSL 114 is obscured by cargo loaded in the cargo bed 118, and send notifications to the VAS ECU 534 and the BCM ECU 528. In other embodiments, the VAS ECU 534 may be configured to execute an object detection algorithm that processes image data received from the rear-facing camera 116 to determine if the primary CHMSL 114 is obscured by cargo loaded in the cargo bed 118, and sends notifications to the BCM ECU 528.
[0067] In certain embodiments, the control system 520 may also include one or more proximity sensor processing (PSP) ECUs that process proximity sensor data received from the proximity sensor 117, determine whether the primary CHMSL 114 is obstructed by cargo loaded in the cargo bed 118, and send notifications to the VAS ECU 534 and the BCM ECU 528. In certain other embodiments, the VASECU 534 may be configured to process proximity sensor data received from the proximity sensor 117, determine whether the primary CHMSL 114 is obstructed by cargo loaded in the cargo bed 118, and then send notifications to the BCM ECU 528.
[0068] In many embodiments, the control system 520 may include, among other things, an autonomous control module (ACM) ECU, an autonomous safety module (ASM) ECU, a battery management system (BMS) ECU, a battery power isolation (BPI) ECU, a balance voltage temperature (BVT) ECU, a door control module (DCM) ECU, a driver monitoring system (DMS) ECU, a near field communication (NFC) ECU, a rear zone control (RZC) ECU, a seat control module (SCM) ECU, a thermal management module (TMM) ECU, a winch control module (WCM) ECU, and the like.
[0069] Figure 6 A sequence diagram 600 of a CHMSL system for a vehicle is shown according to an embodiment of the present disclosure.
[0070] Generally, sequence diagram 600 depicts control system 520 and components that may be associated with the CHMSL system of vehicle 100 , including primary CHMSL 114 , taillights 115 , rear-facing camera 116 , proximity sensor 117 , brake pedal 121 , and wireless auxiliary CHMSL 200 .
[0071] In many embodiments, the data and signals received by the control system 520 include image data 610 and brake pedal signals 620, and the operations performed by the control system 520 include, among other things, determining the brake pedal state and cargo bed state (operation 630), commanding the taillights (operation 640), commanding the main CHMSL (operation 650), and commanding the wireless auxiliary CHMSL (operation 660). The brake pedal state is engaged or disengaged, and the cargo bed state is unobstructed or obstructed.
[0072] In many embodiments, at least one processor of the control system 520 is configured to facilitate activation of a wireless auxiliary CHMSL based on the sensor data. In certain embodiments, at least one processor of the control system 520 is configured to facilitate deactivation of a primary CHMSL based on the sensor data.
[0073] In many implementations, operation 630 may be performed by the VDM ECU 530 and the VAS ECU 534. More specifically, the VDM ECU 530 may be configured to determine the brake pedal state based on the brake pedal signal 620 received from the brake pedal 121, and the VAS ECU 534 may be configured to determine the cargo bed state based on the image data 610. In other implementations, operation 630 may be performed by a single ECU 540.
[0074] When the brake pedal state is the engaged state, the VDM ECU 530 sends a notification to the BCM ECU 528 to turn on the tail light 115 (ie, operation 640 ), and when the brake pedal state is the disengaged state, the VDM ECU 530 sends a notification to the BCM ECU 528 to turn off the tail light 115 (ie, operation 640 ).
[0075] When the cargo bed state is in the unblocked state and the brake pedal state is in the engaged state, the VAS ECU 534 sends a notification to the BCMECU 528 to activate (and open) the main CHMSL 114 (i.e., operation 650); when the cargo bed state is in the unblocked state and the brake pedal state is in the disengaged state, the VAS ECU 534 sends a notification to the BCM ECU 528 to close the main CHMSL 114 (i.e., operation 650). In other words, when the cargo bed state is in the unblocked state, the main CHMSL 114 is activated, and the wireless auxiliary CHMSL 200 is deactivated.
[0076] However, when the cargo bed state is the blocked state and the brake pedal state is the engaged state, the VAS ECU 534 does not send a notification to the BCM ECU 528. Instead, the VAS ECU 534 sends a notification to the VAS ECU 534 to activate (and turn on) the wireless auxiliary CHMSL 200 (i.e., operation 660). Similarly, when the cargo bed state is the blocked state and the brake pedal state is the disengaged state, the VAS ECU 534 does not send a notification to the BCM ECU 528. Instead, the VAS ECU 534 sends a notification to the VAS ECU 534 to turn off the wireless auxiliary CHMSL 200 (i.e., operation 660). In other words, when the cargo bed state is the blocked state, the wireless auxiliary CHMSL 200 is activated, and the main CHMSL 114 is deactivated.
[0077] In certain other embodiments, the data and signals received by the control system 520 include the proximity sensor data 612 and the brake pedal signal 620, and the operation 630 may be performed by the VDM ECU 530 and the VAS ECU 534. More specifically, the VDM ECU 530 may be configured to determine the brake pedal state based on the brake pedal signal 620 received from the brake pedal 121, and the VAS ECU 534 may be configured to determine the cargo bed state based on the proximity sensor data 612. In other embodiments, the operation 630 may be performed by a single ECU 540.
[0078] In further embodiments, the data and signals received by the control system 520 include image data 610, proximity sensor data 612, and brake pedal signal 620, and the operation 630 may be performed by the VDM ECU 530 and the VAS ECU 534. More specifically, the VDM ECU 530 may be configured to determine the brake pedal state based on the brake pedal signal 620 received from the brake pedal 121, and the VAS ECU 534 may be configured to determine the cargo bed state based on the image data 610 and the proximity sensor data 612. In certain other embodiments, the operation 630 may be performed by a single ECU 540.
[0079] Many features and advantages of the present disclosure are apparent from the detailed description, and thus, the appended claims are intended to cover all such features and advantages of the present disclosure that fall within the scope of the present disclosure. Furthermore, since numerous modifications and changes will readily occur to those skilled in the art, it is not desired to limit the present disclosure to the exact construction and operation shown and described, and thus, all suitable modifications and equivalents may be resorted to within the scope of the present disclosure.
Claims
1. A center high mounted stop light (CHMSL) system for a vehicle, comprising: a sensor configured to generate sensor data; a main CHMSL, the main CHMSL comprising a main lamp; A wireless assisted CHMSL, the wireless assisted CHMSL comprising: Auxiliary lights, a control circuit coupled to the auxiliary light, the control circuit comprising a CHMSL wireless transceiver and a microcontroller, and a battery, the battery being coupled to the control circuit, the battery being configured to power the auxiliary light and the control circuit; Vehicle wireless transceiver; and at least one processor coupled to the sensor, the master CHMSL, and the vehicle wireless transceiver, the at least one processor configured to: Activation of the wireless assisted CHMSL is facilitated based on the sensor data.
2. The CHMSL system of claim 1, wherein said facilitation comprises: determining whether the primary CHMSL is obstructed based on the sensor data, When the main CHMSL is obscured: in response to receiving the brake engagement signal, sending an activation message to the wireless auxiliary CHMSL via a wireless communication link; in response to receiving a brake disengagement signal, sending a deactivation message to the wireless auxiliary CHMSL via the wireless communication link; When the main CHMSL is not obstructed: in response to receiving the brake engagement signal, sending the activation message to the master CHMSL via a wired communication link; as well as In response to receiving the brake disengagement signal, the deactivation message is sent to the master CHMSL via the wired communication link.
3. The CHMSL system of claim 2, wherein the control circuit is configured to: turning on the auxiliary light in response to receiving the activation message; and The auxiliary light is turned off in response to receiving the deactivation message. 4 . The CHMSL system of claim 2 , wherein the brake engage signal and the brake disengage signal are generated by a brake pedal of the vehicle, the brake pedal being configured to communicate with the at least one processor.
5. The CHMSL system of claim 1, wherein the sensor is a camera positioned adjacent to the primary CHMSL having a view of a cargo area of the vehicle.
6. The CHMSL system of claim 5, wherein the cargo area includes a cargo bed and a track, and the wireless assisted CHMSL is mounted to the track.
7. The CHMSL system of claim 2, wherein the microcontroller and the CHMSL wireless transceiver are packaged in a single module.
8. The CHMSL system according to claim 7, wherein: The vehicle wireless transceiver is a Bluetooth transceiver; The auxiliary light includes one or more light emitting diodes (LEDs) coupled to a light emitting diode (LED) drive circuit; The CHMSL wireless transceiver is a Bluetooth transceiver; and The wireless communication link is a Bluetooth low energy communication link.
9. The CHMSL system of claim 2, wherein: The control circuit includes a battery sensor coupled to the battery, the battery sensor configured to generate a battery charging signal; and The control circuit is configured to: determining a battery charge level based on the battery charge signal, generating a first status message including the battery charge level, and The first status message is transmitted to the at least one processor via the wireless communication link.
10. The CHMSL system of claim 9, wherein the control circuit is configured to: determining a fault condition of at least one of the battery, the auxiliary light, the CHMSL wireless transceiver, and the microcontroller, generating a second status message including the fault status, and The second status message is transmitted to the at least one processor via the wireless communication link.
11. The CHMSL system of claim 10, wherein the at least one processor is configured to send the battery charge level and the fault status to a display of the vehicle.
12. A wireless central high mounted stop light (CHMSL), comprising: lamp; a control circuit coupled to the lamp, the control circuit comprising: A wireless transceiver, the wireless transceiver being configured to: transmitting messages to the vehicle via a wireless communication link, and receiving a message from the vehicle via the wireless communication link, and A microcontroller, the microcontroller being configured to: turning on the light in response to receiving an activation message transmitted from the vehicle via the wireless communication link, and turning off the light in response to receiving a deactivation message transmitted from the vehicle via the wireless communication link; a battery coupled to the control circuit, the battery configured to power the light and the control circuit; and A housing is provided for the light, the control circuit and the battery, the housing being configured to be mounted to the vehicle.
13. The wireless CHMSL of claim 12, wherein the housing is configured to be mounted to a cargo bed rail of the vehicle.
14. The wireless CHMSL of claim 12, wherein the wireless communication link is an Institute of Electrical and Electronics Engineers (IEEE) 802.11 communication link.
15. The wireless CHMSL of claim 12, wherein the wireless transceiver and the microcontroller are packaged in a single module.
16. The wireless CHMSL of claim 15, wherein: The lamp includes one or more light emitting diode (LED) coupled to a light emitting diode (LED) driver circuit; The wireless transceiver is a Bluetooth transceiver; and The wireless communication link is a Bluetooth low energy communication link.
17. The wireless CHMSL of claim 16, further comprising a Bluetooth pairing button coupled to the microcontroller and mounted on the housing.
18. The wireless CHMSL of claim 12, wherein: The control circuit includes a battery sensor coupled to the battery, the battery sensor configured to generate a battery charging signal; and The control circuit is configured to: determining a battery charge level based on the battery charge signal, generating a first status message including the battery charge level, and The first status message is transmitted to the vehicle via the wireless communication link.
19. The wireless CHMSL of claim 18, wherein the control circuit is configured to: determining a fault condition of at least one of the battery, the light, the wireless transceiver, and the microcontroller, generating a second status message including the fault status, and The second status message is transmitted to the vehicle via the wireless communication link.
20. The wireless CHMSL of claim 19, further comprising: Battery charging port, The control circuit includes a battery charger coupled to the battery charging port and the battery sensor, and the battery charger is configured to charge the battery.
