Vehicle lamp control method and vehicle

Abstract

The invention provides a vehicle lamp control method and a vehicle. The method is applied to a vehicle, the vehicle comprises a vehicle lamp control system, and the vehicle lamp control system comprises a lamp controller, an interactive display device, a first lamp set and a domain controller; the lamp controller is connected with the interactive display device, the first lamp group and the domain controller, the computing power of the lamp controller is lower than that of the domain controller, and the method comprises the following steps: receiving a control signal sent by the domain controller through the lamp controller; and controlling the display content of one or more items in the interactive display device and the first lamp group through the lamp controller based on the control signal. According to the invention, the control of a large number of LEDs is realized.

Description

Technical Field

[0001] This application relates to the field of intelligent vehicle technology, and in particular to a vehicle lighting control system and vehicle. Background Technology

[0002] Intelligent new energy electric vehicles are the mainstream development direction both domestically and internationally. These vehicles especially require warm and intelligent designs, with colorful and dynamic interior ambient lighting and intelligent dot-matrix interactive screens becoming design highlights. As technology advances and consumers' demands for interior ambient lighting and interactive screens increase, particularly in terms of the color of ambient lighting, the number of light-emitting diodes (LEDs), and the grayscale levels and number of LEDs on interactive screens, the requirements for microcontroller units (MCUs) control resources and bus speeds are increasing, posing challenges to the transmission and display of large amounts of data.

[0003] However, the architecture design and control methods for interior ambient lighting and exterior interactive screens in related technologies are independent and decentralized, only solving the problem of whether ambient lighting and interactive screens are present, and failing to meet the dynamic control of a large number of LEDs. Summary of the Invention

[0004] This application provides a vehicle lighting control method and a vehicle.

[0005] The technical solution of this application is implemented as follows: In a first aspect, a vehicle lighting control method is provided, applied to a vehicle, the vehicle including a vehicle lighting control system, the vehicle lighting control system including: a lamp controller, an interactive display device, a first lamp group, and a domain controller; the lamp controller is connected to the interactive display device, the first lamp group and the domain controller, the computing power of the lamp controller is lower than the computing power of the domain controller, the method includes: receiving a control signal sent by the domain controller through the lamp controller; and controlling the display content of one or more of the interactive display device and the first lamp group based on the control signal through the lamp controller.

[0006] In this embodiment, a single lamp controller simultaneously controls both the lamp group and the display interaction device. This eliminates the need for integrated development, testing, and management of the control modules corresponding to the lamp group and the display interaction device, saving costs and enabling systematic control of both the lamp group and the display interaction device. Furthermore, the lamp controller controls the playback of lighting effects on the lamp group and the display interaction device based on signals sent by the domain controller, achieving precise control of a large number of LEDs.

[0007] In some embodiments, the vehicle lighting control system further includes a storage device connected to the lighting controller and communicating with the lighting controller via an internal synchronous serial peripheral interface; the step of controlling the display content of one or more of the interactive display device and the first lighting group based on the control signal includes: obtaining lighting effect data matching the control signal from the storage device; and controlling the display content of one or more of the interactive display device and the first lighting group based on the lighting effect data.

[0008] In this embodiment, the light controller adds an external storage device for unified storage of lighting effects of interior ambient lighting and animation effects of interactive screen. During storage, it remembers the data addresses of different data and supports mixed storage of different video data, thereby improving storage space utilization. When there is a need for lighting effect playback, the corresponding data can be quickly obtained from the storage device.

[0009] In some embodiments, controlling the display content of one or more of the interactive display device and the first light group based on the lighting effect data includes: if the control signal is used to control the interactive display device, sending a first message to the interactive display device; wherein the first message is used to obtain the status of the interactive display device; if the status of the interactive display device is successfully obtained and the status is a fault-free state, reading the first animation to be presented from the lighting effect data; sending a first request to the interactive display device; wherein the first request is used to request the transmission of the first animation; if a first response is received, and the first response indicates that the interactive display device is ready to receive the first animation, sending the first animation and a message indicating that the first animation has been sent; if a second response is received, and the second response indicates that the interactive display device has successfully received the first animation, continuing to send a request to the interactive display device to request the transmission of a second animation, and sending the second animation to the interactive display device when the interactive display device is ready to receive the second animation, until the interactive display device successfully receives or presents the lighting effect data; wherein the lighting effect data includes the first animation and the second animation; the second animation is data after the first animation.

[0010] In this embodiment of the application, the status of the interactive display device can be obtained in a timely manner while controlling the content presented by the interactive display device through a request feedback mechanism.

[0011] In some embodiments, the first request further indicates that if the interactive display device is not allowed to refresh the screen during the sending of the first animation in the first N frames, the interactive display device is allowed to refresh the screen when sending the N+1th frame; the method further includes: if a first response is not received, or the first response indicates that the interactive display device is malfunctioning, or the first response indicates that the interactive display device cannot receive the first animation, resend the first request M times; where N and M are positive integers; if the lighting effect data presentation is completed, send a second request to the interactive display device through the light controller; wherein the second request is used to instruct the interactive display device to turn off the screen; through the interactive display device, turn off all displays on the screen and send a third response to the light controller; the third response indicates that the interactive display device has successfully turned off the screen.

[0012] In this embodiment of the application, by requesting retransmission, the situation where the lamp controller misses the relevant response is avoided. After the presentation is completed, the interactive display device is instructed to turn off the screen in a timely manner through the corresponding instruction, thus saving resources.

[0013] In some embodiments, controlling the display content of one or more of the interactive display device and the first light group based on the lighting effect data includes: if the control signal is used to control the first light group, sending a second message to the first light group; wherein the second message is used to instruct the first light group to periodically adjust the color and brightness of each light to match the lighting effect data.

[0014] In this embodiment, the color and brightness of the ambient light are periodically controlled by a light controller.

[0015] In some embodiments, the method further includes: detecting fault conditions of the first lamp group and the interactive display device through a lamp controller; if fault information is detected, performing one or more of the following operations: storing the fault information in the storage device; and reporting the fault information.

[0016] In this embodiment, the working and fault status of ambient lights and interactive screens can be directly monitored through the light controller, and relevant information can be stored and reported to facilitate after-sales maintenance and repair of parts.

[0017] In some embodiments, the data stored in the storage device includes one or more of the following: a first identifier for the lighting effect to be presented; the total number of lighting effect frames to be presented; a second identifier for the currently pre-presented frame; the number of lights to be lit corresponding to the second identifier; and the number of controller local network frames at a flexible data rate to be sent corresponding to the second identifier. The method further includes: if the data stored in the storage device is updated before mass production, rewriting the data stored in the storage device and re-identifying the starting address of each lighting effect data; if the data stored in the storage device is updated after mass production, writing target data into the blank storage space of the storage device and identifying the starting address of the target data; wherein the blank storage area is a reserved area in the storage device located in the last segment of the storage device.

[0018] In this embodiment, different update methods are used to update the data in the storage device at different times, so that the vehicle lighting control system supports data updates and replacements, and the video data content can be flexibly adjusted.

[0019] In some embodiments, the method further includes: if the storage block corresponding to the first data is a faulty block, identifying the faulty block and shifting the storage location corresponding to the first data to the next position; the first data is data to be stored in the storage device.

[0020] This application provides a bad block management scheme that avoids the waste of resources caused by storing other data requests in bad blocks by recording bad blocks.

[0021] In some embodiments, the lamp controller communicates with the first lamp group via a local interconnect network bus or a first flexible data rate controller local network bus; the lamp controller communicates with the interactive display device via a second flexible data rate controller local network bus; the lamp controller communicates with the domain controller via a controller local network bus or a third flexible data rate controller local network bus; wherein, the communication rate corresponding to the first flexible data rate controller local network bus is less than the communication rate corresponding to the second flexible data rate controller local network bus; the communication rate corresponding to the first flexible data rate controller local network bus is equal to the communication rate corresponding to the third flexible data rate controller local network bus; and the communication rate corresponding to the controller local network bus is less than the communication rate corresponding to the controller local network bus.

[0022] In this embodiment, the lamp controller transmits data via CAN FD bus and LIN bus to achieve the playback of the target lighting effect, thereby reducing data transmission costs.

[0023] Secondly, embodiments of this application provide a vehicle, the vehicle comprising: a memory for storing executable instructions; and a processor for executing the executable instructions stored in the memory to implement the steps in the above method.

[0024] Thirdly, this application provides a vehicle lighting control system, which includes: a lamp controller, an interactive display device, a first lamp group, and a domain controller; the lamp controller is connected to the interactive display device, the first lamp group, and the domain controller, and the computing power of the lamp controller is lower than that of the domain controller. The lamp controller is used to receive control signals sent by the domain controller; The lamp controller is also used to control the display content of one or more of the interactive display device and the first lamp group based on the control signal.

[0025] Fourthly, a computer-readable storage medium is provided having a computer program stored thereon, which, when executed by a processor, implements some or all of the steps in the above-described method.

[0026] Fifthly, a computer program product is provided, comprising a computer program or instructions that, when executed by a processor, implement some or all of the steps in the above-described method. Attached Figure Description

[0027] Figure 1 A schematic diagram of a vehicle lighting control system provided in this application embodiment. Figure 1 ; Figure 2 A schematic diagram of a vehicle lighting control system provided in this application embodiment. Figure 2 ; Figure 3 This is a schematic diagram of an interactive screen provided in an embodiment of this application; Figure 4 This is a schematic diagram of the full-screen resolution of an interactive screen provided in an embodiment of this application; Figure 5 This is a schematic diagram illustrating the effective resolution of an interactive screen provided in an embodiment of this application; Figure 6 This is a schematic diagram of the LED arrangement of an interactive screen provided in an embodiment of this application; Figure 7 A schematic flowchart illustrating a vehicle lighting control method provided in an embodiment of this application; Figure 8 This is the timing diagram of the MCU3 response to the fault provided in this application; Figure 9 This is the timing diagram of the MCU2 timeout failure provided in this application; Figure 10This is a timing diagram of the normal state provided in this application; Figure 11 This is a timing diagram of a normal transmission of one frame, provided in this application; Figure 12 This is a timing diagram of a normal animation transmission method provided in this application; Figure 13 This is a timing diagram of an MCU3 fault recovery method provided in this application; Figure 14 This application provides a timing diagram for an MCU2 that times out and does not respond. Figure 15 This is a timing diagram of an MCU3 timeout failure provided in this application; Figure 16 This application provides a timing diagram for an MCU3 timeout response to a data error. Figure 17 This application provides a timing diagram for a fault that the MCU3 cannot display. Figure 18 This is a timing diagram of a normal control screen shutdown provided in this application; Figure 19 This application provides a timing diagram for an MCU3 responding to an error in a screen-off command. Figure 20 This application provides a timing diagram for an MCU2 that fails to respond to a screen-off command after a timeout. Figure 21 This is a schematic diagram of an LED bead corresponding to an interactive screen provided in an embodiment of this application; Figure 22 This is a flowchart of the update scheme provided in this application; Figure 23 This is a schematic diagram of a hardware entity of a vehicle in an embodiment of this application. Detailed Implementation

[0028] To make the objectives, technical solutions, and advantages of this application clearer, the technical solutions of this application are further described in detail below with reference to the accompanying drawings and embodiments. The described embodiments should not be regarded as limitations on this application. All other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0029] In the following description, references are made to “some embodiments,” which describe a subset of all possible embodiments. However, it is understood that “some embodiments” may be the same subset or different subsets of all possible embodiments and may be combined with each other without conflict.

[0030] The terms “first / second / third” are used merely to distinguish similar objects and do not represent a specific ordering of objects. It is understood that “first / second / third” may be interchanged in a specific order or sequence where permitted, so that the embodiments of this application described herein can be implemented in an order other than that illustrated or described herein.

[0031] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application pertains. The terminology used herein is for descriptive purposes only and is not intended to be limiting of this application.

[0032] Figure 1 This is a schematic diagram of a vehicle lighting control system provided in an embodiment of this application, as shown below. Figure 1 As shown, the system includes: a lamp controller 101, an interactive display device 102, a first lamp group 103, and a domain controller 104; the lamp controller 101 is connected to the interactive display device 102, the first lamp group 103, and the domain controller 104. The lamp controller 101 communicates with the first lamp group 103 via a Local Interconnect Network (LIN) bus or a Controller Area Network with Flexible Datarate (CAN FD) bus. The lamp controller 101 communicates with the interactive display device 102 via the second CAN FD bus; The lamp controller 101 communicates with the domain controller 104 via a CAN bus or a third CAN FD bus; The communication rate corresponding to the first CAN FD is less than the communication rate corresponding to the second CAN FD; the communication rate corresponding to the first CAN FD is equal to the communication rate corresponding to the third CAN FD; the communication rate corresponding to CAN is less than the communication rate corresponding to the first CAN FD. For example, the first CAN FD corresponds to a 2M communication rate; the second CAN FD corresponds to a 5M communication rate; the third CAN FD corresponds to a 2M communication rate; and CAN corresponds to a 500K communication rate.

[0033] In this embodiment of the application, the domain controller 105 includes a body domain controller (BDC) and a cockpit domain controller (CDC).

[0034] In this embodiment, the first light group is a light group of various shapes composed of multiple LEDs, such as a breathing ambient light and a flowing ambient light.

[0035] In this embodiment of the application, the interactive display device, also known as an interactive screen, interactive display screen, or display screen, is a device installed in a vehicle that can interact with a first object.

[0036] Here, the first object includes people inside the vehicle, such as the driver in the front seat or the passenger in the front passenger seat.

[0037] In some embodiments, the vehicle lighting control system further includes a storage device; the storage device is directly connected to the lighting controller and communicates with the lighting controller via an internal synchronous serial peripheral interface (SPI).

[0038] It should be noted that, due to cost and installation space limitations, the design of vehicle lighting groups and interactive display devices in related technologies does not support direct transmission of Ethernet and video data. The storage and management of large amounts of data is a challenge. Therefore, this application adds a storage device, such as an external flash memory chip, to the lighting controller for unified storage of lighting effects of interior ambient lighting and animation effects of interactive screens. During storage, the data addresses of different data are remembered, and different video data can be mixed for storage, thereby improving the utilization rate of storage space.

[0039] Figure 2 A schematic diagram of a vehicle lighting control system provided in this application embodiment is shown below. Figure 2 As shown, the vehicle lighting control system 100 includes: a lighting controller 101 (such as a Lighting Signal Controller (LSC)), an interactive display device 102 (such as an interactive screen), a first lighting group 103 (such as a group consisting of 24 breathing ambient lights and 6 flowing ambient lights including flowing ambient light assembly 1 (right), flowing ambient light assembly 1 (left), flowing ambient light assembly 2 (right), flowing ambient light assembly 2 (left), flowing ambient light assembly 3 (right), and flowing ambient light assembly 3 (left)), and a domain controller 104 (such as a CDC and a BDC); the lighting controller 101 is directly connected to the interactive display device 102, the first lighting group 103, and the domain controller 104; The LSC is connected to 6 flowing ambient lights via CAN FD1, to the interactive screen via CAN FD2, to 24 breathing ambient lights via LIN1 / LIN2 / LIN3 / LIN4, to the CDC via CAN FD3, and to the BDC via CAN. The LSC and the 6 flowing ambient lights are connected to the KL30 power supply of the vehicle (BDC), and the breathing ambient lights are connected to the KL15 power supply of the vehicle (BDC).

[0040] In some embodiments, the body domain controller connects to the LSC via a CAN (500K communication rate) bus, providing signals such as vehicle function requests to the LSC and UDS diagnostic communication; it provides power to the LSC and the flowing ambient lighting via KL30, and provides power to the breathing ambient lighting via KL15.

[0041] In some embodiments, the cockpit domain controller provides signals for the vehicle to request functions from the LSC, transmit data, and interact with status via the CAN FD3 (2M communication rate) bus.

[0042] In some embodiments, the LSC includes an MCU module, a flash module, a CAN transceiver module, a CAN FD transceiver module, a DC-DC converter module, and a CAN FD module; wherein, the Motor Control Unit (MCU) module controls the left front midrange speaker, the right front midrange speaker, the rear left front woofer, the rear right front woofer, and the subwoofer; the DC-DC converter communicates with the MCU module through the CAN FD module in the LSC; the MCU module is connected to the flash module through an SPI interface; the six ambient lights communicate with the MCU module through the CAN FD transceiver module in the LSC; the interactive screen communicates with the MCU module through the CAN FD transceiver module in the LSC; the BDC converter communicates with the MCU module through the CAN transceiver module in the LSC; and the DC-to-DC converter (DCDC) module of the LSC is connected to the KL30 power supply of the vehicle (BDC).

[0043] The computing power of the lamp controller is lower than that of the domain controller. Here, the LSC capabilities include: MUC main frequency: 160MHz; MCU Random Access Memory (RAM): 256K; MCU Read-Only Memory (ROM): 2M; flash: 128M, which can store about 300s of screen animation and 3000 images.

[0044] In some embodiments, the 24 breathing ambient lights include 6 breathing ambient lights connected via LIN1; 6 breathing ambient lights connected via LIN2; 6 breathing ambient lights connected via LIN3; and 6 breathing ambient lights connected via LIN4; that is, 6 breathing ambient lights per LIN channel. Here, each of the 24 breathing ambient lights has 1 LED, supports 256 color switching, and has 100 adjustable brightness levels.

[0045] In some embodiments, the flowing ambient light assembly 1 (right) includes a CAN FD transceiver module, an MCU4, an LED driver, and LEDs. Here, the flowing ambient light assembly 1 (right) includes four LEDs, each supporting 256 color switching options and 100 levels of adjustable brightness.

[0046] In some embodiments, the flowing ambient light assembly 1 (left) includes a CAN FD transceiver module, an MCU5, an LED driver, and LEDs. Here, the flowing ambient light assembly 1 (left) has 4 LEDs, each supporting 256 color switching options and 100 levels of adjustable brightness.

[0047] In some embodiments, the flowing ambient light assembly 2 (right) includes a CAN FD transceiver module, an MCU6, an LED driver, and LEDs. Here, the flowing ambient light assembly 2 (right) has 19 LEDs, each supporting 256 color switching options and 100 levels of adjustable brightness.

[0048] In some embodiments, the flowing ambient light assembly 2 (left) includes a CAN FD transceiver module, an MCU7, an LED driver, and LEDs. Here, the flowing ambient light assembly 2 (left) has 19 LEDs, each supporting 256 color switching options and 100 levels of adjustable brightness.

[0049] In some embodiments, the flowing ambient light assembly 3 (right) includes a CAN FD transceiver module, an MCU8, an LED driver, and LEDs. Here, the flowing ambient light assembly 3 (right) has 39 LEDs, each supporting 256 color switching options and 100 levels of adjustable brightness.

[0050] In some embodiments, the flowing ambient light assembly 3 (left) includes a CAN FD transceiver module, an MCU9, an LED driver, and LEDs. Here, the flowing ambient light assembly 3 (left) has 39 LEDs, each supporting 256 color switching options and 100 levels of adjustable brightness.

[0051] In some embodiments, the interactive screen includes three CAN FD transceiver modules, MCU1, MCU2, MCU3, three DC-DC converters, three LED drivers, and an LED light board.

[0052] Figure 3 This is a schematic diagram of an interactive screen provided in an embodiment of this application; Figure 3 As shown, 301 is the light-emitting area of ​​the interactive screen, with overall dimensions of 1252mm * 151mm and a light-emitting area of ​​approximately 0.17m². 2 .

[0053] Figure 4 This is a schematic diagram of the full-screen resolution of an interactive screen provided in an embodiment of this application; Figure 4 As shown, the full-screen resolution of the interactive screen is 306*63.

[0054] Figure 5 This is a schematic diagram illustrating the effective resolution of an interactive screen provided in an embodiment of this application; Figure 5 As shown, the effective resolution of the interactive screen is 306*38.

[0055] Figure 6 This is a schematic diagram of the LED arrangement of an interactive screen provided in an embodiment of this application; as shown... Figure 6 As shown, the LEDs are arranged horizontally and vertically, rather than following the curves of the shape boundary; the center-to-center spacing of the LEDs is 4.1mm, the light-emitting diameter is 2.4mm, and the light-emitting boundary is square. Due to the higher brightness in the middle, the visual effect is circular; within the light-emitting boundary, there are octagonal darker illuminated areas and circular brighter illuminated areas.

[0056] The number of LEDs can be set to 10,500; Table 1 is a grayscale table corresponding to the LED brightness capability provided in this application. As shown in Table 1, the LED brightness capability is 32 grayscale levels.

[0057]

[0058] Table 1 Interactive screen electronic capabilities: MCU1 / MCU2 / MCU3: main frequency: 150MHz; RAM: 256K; ROM: 2M; screen refresh rate: 1920Hz; image refresh rate: 33.3Hz.

[0059] Figure 7 This is a schematic diagram illustrating the implementation flow of a vehicle lighting control method provided in an embodiment of this application. The vehicle lighting control method is applied to a vehicle lighting control system, which includes a lamp controller, an interactive display device, a first lamp group, and a domain controller. Figure 7 As shown, this control method can be implemented through steps 701 to 702: Step 701: Receive control signals sent by the domain controller through the lamp controller.

[0060] Step 702: Using the lamp controller, based on the control signal, control the display content of one or more of the interactive display devices and the first lamp group.

[0061] In this embodiment of the application, the control signals include requests, data, and Unified Diagnostic Services (UDS) diagnostic signals sent by BDC / CDC.

[0062] In this embodiment, the control signal can control the interactive display device to display corresponding content, or control the first light group to display related content; it can also simultaneously control the interactive display device and the first light group to jointly display a certain content.

[0063] For example, the light controller can receive requests, data, and Unified Diagnostic Services (UDS) signals from a domain controller (such as a BDC / CDC) via CAN / CAN FD3.

[0064] In this embodiment, the computing power of the lamp controller is lower than that of the domain controller; the lamp controller communicates with the first lamp group via a local interconnect network bus or a first flexible data rate controller local network bus; the lamp controller communicates with the interactive display device via a second flexible data rate controller local network bus; the lamp controller communicates with the domain controller via a controller local network bus or a third flexible data rate controller local network bus; wherein, the communication rate corresponding to the first flexible data rate controller local network bus is less than the communication rate corresponding to the second flexible data rate controller local network bus; the communication rate corresponding to the first flexible data rate controller local network bus is equal to the communication rate corresponding to the third flexible data rate controller local network bus; and the communication rate corresponding to the controller local network bus is less than the communication rate corresponding to the first flexible data rate controller local network bus.

[0065] In some embodiments, the vehicle lighting control system further includes a storage device connected to the lighting controller and communicating with the lighting controller via an internal synchronous serial peripheral interface; the step 702, controlling the display content of one or more of the interactive display device and the first light group based on the control signal, can be achieved through the following steps: Step A1: Obtain the lighting effect data that matches the control signal from the storage device.

[0066] Step A2: Based on the lighting effect data, control the display content of one or more of the interactive display devices and the first light group.

[0067] In this embodiment of the application, the storage device stores the lighting effect data of the interactive display device and the first lamp group.

[0068] In this embodiment, the lamp controller reads internal flash lighting effect data through internal synchronous SPI communication, transmits data through CAN FD1 / LIN1 / LIN2 / LIN3 / LIN4 respectively, and controls the color and brightness of the flowing ambient light LED and the breathing ambient light LED; it also transmits data through CAD FD2 to control the interactive display screen.

[0069] For example, the color and brightness of the breathing ambient light LED can be switched every 10ms cycle (calibration supported), or the color and brightness of the flowing ambient light LED can be switched every 8ms cycle (calibration supported) to achieve dynamic lighting effects playback of the ambient light.

[0070] For example, each frame of lighting data can be transmitted in a 30ms cycle (calibration supported), the lighting grayscale of the LED can be controlled, and the grayscale and on / off status of the LED can be quickly switched to achieve dynamic lighting effect playback on the interactive screen.

[0071] Here, the lighting controller receives function request signals from the vehicle. When it is necessary to control the ambient lighting to display a specific effect, the LSC reads the corresponding animation data and transmits data and control signals through the CAN FD bus and LIN bus to achieve the playback of the target lighting effect. When it is necessary to control the interactive screen to display a specific effect, the lighting controller reads the corresponding animation data and transmits data and control signals through the CAN FD bus. Through specific signal logic and timing design, the target lighting effect is played.

[0072] In some embodiments, step A2, which involves controlling the display content of one or more of the interactive display device and the first light group based on the lighting effect data, can be achieved through step B1 or through step B2: Step B1: If the control signal is used to control the interactive display device, send a first message to the interactive display device; wherein the first message is used to obtain the status of the interactive display device; if the status of the interactive display device is successfully obtained and the status is fault-free, read the first animation to be presented from the lighting effect data; send a first request to the interactive display device; wherein the first request is used to request the transmission of the first animation; if a first response is received, and the first response indicates that the interactive display device is ready to receive the first animation, send the first animation and a message indicating that the first animation has been sent; if a second response is received, and the second response indicates that the interactive display device has successfully received the first animation, continue to send a request to the interactive display device to request the transmission of the second animation, and send the second animation to the interactive display device when the interactive display device is ready to receive the second animation, until the interactive display device successfully receives or presents the lighting effect data; wherein the lighting effect data includes the first animation and the second animation; the second animation is the data after the first animation.

[0073] In some embodiments, the first request further indicates that during the transmission of the first animation, if the interactive display device is not allowed to refresh the screen during the first N frames, the interactive display device is allowed to refresh the screen during the transmission of the N+1th frame; N is a positive integer.

[0074] In some embodiments, if the first response is not received, or the first response indicates a malfunction of the interactive display device, or the first response indicates that the interactive display device cannot receive the first animation, the first request is resent M times; M is a positive integer.

[0075] In some embodiments, once the lighting effect data presentation is complete, a second request is sent to the interactive display device via the light controller; wherein the second request is used to instruct the interactive display device to turn off the screen; the interactive display device turns off all displays on the screen and sends a third response to the light controller; the third response indicates that the interactive display device has successfully turned off the screen.

[0076] In some embodiments, the steps of the lamp controller controlling the display content of the interactive display device are as follows: a. Do not send any CANFD signals to the interactive screen after the controller is powered on or woken up; b. It is necessary to wait for the interactive screen to display relevant control commands; c. When there is a need for interactive screen display (screen display triggered), start periodically sending LSC_001 messages, outputting control command (LSC_control) as 0 (i.e., 0x00:), and light controller state (LSC_state) as 0 (i.e., 0x00:); and send event LSC_202 signal command request (command_request) as 0x05 to obtain the status of the 3 nodes of the HALO screen (i.e., the first message); Where LSC_control is 0x00: indicates that periodic screen refresh is not allowed; LSC_control is 0x01: indicates that periodic screen refresh is allowed; LSC_control is 0x02: indicates entering sleep mode. LSC_state of 0x00 indicates no video output; LSC_state of 0x01 indicates that animation data is being sent.

[0077] LSC_001 also includes a message frame count (frame_count); The LSC_202 includes the following: command request (command_reques), current animation index number (Animation_ID), total number of frames in the currently transmitted animation (Total_animation_picture, or 1 if it's a single image), current number of frames in the animation (or 1 if it's a single image) (current_animation_picture), number of LEDs lit by MCU1 in this frame (Number_light_beads1), total number of data frames sent by MCU1 in this frame (number_frame1), number of LEDs lit by MCU2 in this frame (Number_light_beads2), total number of data frames sent by MCU2 in this frame (number_frame2), number of LEDs lit by MCU3 in this frame (Number_light_beads3), total number of data frames sent by MCU3 in this frame (number_frame3), and frame count (frame_count). Among them, command_request 0x00 indicates an invalid request (no response required); command_request 0x01 indicates a screen data transmission request; command_request 0x02 indicates screen data transmission stopped; command_request 0x03 indicates screen data retransmission; command_request 0x04 indicates screen data transmission completed; command_request 0x05 indicates screen controller status acquisition; command_request 0x06 indicates screen diagnostics started (acquired after 200ms); command_request 0x07 indicates screen diagnostic status acquisition; and command_request 0x08 indicates screen off control.

[0078] Animation_ID of 0x0000 indicates when the command_request is 0x00, 0x05, 0x06, or 0x07; Animation_ID of 0x1XXX indicates image mode, XXX mode number, when the command_request is 0x01, 0x02, 0x03, or 0x04; Animation_ID of 0x2XXX indicates animation mode, XXX mode number, when the command_request is 0x01, 0x02, 0x03, or 0x04. A Total_animation_picture value of 0x0000 indicates that the value is 0 when the command_request is 0x00, 0x05, 0x06, or 0x07; a Total_animation_picture value of 0x0001-0xFFFF indicates that the value is 0 when the command_request is 0x01, 0x02, 0x03, or 0x04; the value is determined based on the actual number of animation frames currently being animated. A current_animation_picture value of 0x0000 indicates that the command_request value is 0x00, 0x05, 0x06, or 0x07; a current_animation_picture value of 0x0001-0xFFFF indicates that the command_request value is 0x01, 0x02, 0x03, or 0x04; the value is determined based on the current actual number of animation frames. Number_light_beads1, number_frame1, Number_light_beads2, number_frame2, Number_light_beads3, and number_frame3 are only valid references when command_request is 0x04; otherwise, they are 0. d. If a timeout of 10ms occurs during the status acquisition process and no one of the following is received: HALO_NOTE1_301 for MCU1, HALO_NOTE2_302 for MCU2, or HALO_NOTE3_303 for MCU3, or if a reply is received but the error message err_define!=0 is not found, 20 retry attempts are required (to address the issue of a response only being available 60ms after wake-up). Figure 8 This is the timing diagram of the MCU3 response to the fault provided in this application, such as... Figure 8 As shown, if the HALO_NOTE3_303 response for MCU3 fails, it will retry 20 times. If it fails 20 times, the fault will be recorded.

[0079] Among them, HALO_NOTE1_301, HALO_NOTE2_302 and HALO_NOTE3_303 include command response, current animation index number, total number of frames of the currently transmitted animation (1 if it is a single image) (Total_animation_picture), current number of frames of the animation (1 if it is a single image) (current_animation_picture), current control state, controller fault type (err_define), and frame count (frame_count).

[0080] Here, `command_respond` of 0x01 indicates readiness to receive data, responding with `command_request = 0x01 / 0x03`; `command_respond` of 0x02 indicates readiness to receive new data, responding with `command_request = 0x01 / 0x03`; `command_respond` of 0x03 indicates correct reception of the current frame, responding with the command `command_request = 0x04`, responding upon receipt; `command_respond` of 0x04 indicates an error in the current frame reception, with an incorrect data frame ID, responding with the command `command_request = 0x04`, responding upon receipt; `command_respond` of 0x05 indicates an error in the currently received data, with an incorrect data frame content, responding with the command `command_request = 0x04`, responding upon receipt; `command_respond` of 0x06 indicates an internal malfunction in the actuator, preventing output control, responding with the command `command_request = 0x04`. Upon receiving the command, a response is initiated; a command_respond of 0x07 indicates diagnostics are in progress, and a response is initiated upon receiving the command "command_request=0x06"; a command_respond of 0x08 indicates the receiving process has been exited and the buffer has been cleared, and a response is initiated upon receiving the command "command_request=0x02"; a command_respond of 0x09 indicates the current screen controller status is being reported, and a response is initiated upon receiving the command "command_request=0x05 / 0x07"; a command_respond of 0x0a indicates the screen has been controlled to turn off, and a response is initiated upon receiving the command "command_request=0x08"; other values ​​of command_respond indicate invalidity. Animation_ID of 0x0000 represents the initial value after power-on or wake-up; Animation_ID of 0x0001-0x2FFF represents the index value of the last received LSC transmission (buffered in RAM). Total_animation_picture of 0x0000 represents the initial value after power-on or wake-up; Total_animation_picture of 0x0001-0xFFFF represents the index value of the last received LSC transmission (cached in RAM). The current_animation_picture value of 0x0000 represents the initial value after power-on or wake-up; the current_animation_picture value of 0x0001-0xFFFF represents the index value of the last LSC transmission received (buffered in RAM). Current_control_state = 0x00 indicates the screen is off or idle; Current_control_state = 0x01 indicates the state during animation refresh; Current_control_state = 0x02 indicates the state during the display of the last image; Current_control_state = 0x03 indicates a malfunction that prevents output display. err_define bit0 indicates undervoltage fault; err_define bit1 indicates overvoltage fault; err_define bit2 indicates open circuit fault; err_define bit3 indicates short circuit fault; err_define bit4 indicates overtemperature fault.

[0081] e. If all 20 attempts fail, report the corresponding fault on the interactive screen (node ​​loss or corresponding fault value). Figure 9 This is the timing diagram for the MCU2 timeout failure provided in this application. (Example:) Figure 9 As shown, if HALO_NOTE3_303 corresponding to MCU3 does not reply with any content, then retry 20 times. If all 20 attempts fail, then record the fault.

[0082] f. If communication is successful and both receive command_respond 0x09: Current screen controller status report, then proceed to the data packet sending process. Figure 10 This is the timing diagram of the normal state provided in this application; after successfully receiving all MCU replies reporting a fault err_define!=0, the process switches to the screen sending process, and it takes 60ms after the interactive screen wake-up is activated before it can respond.

[0083] Figure 11This is a timing diagram of a normal transmission of one frame, provided in this application; Figure 12 This is a timing diagram of a normal animation transmission method provided in this application; Figure 13 This is a timing diagram of an MCU3 fault recovery method provided in this application; Figure 14 This application provides a timing diagram for an MCU2 that times out and does not respond. Figure 15 This is a timing diagram of an MCU3 timeout failure provided in this application; Figure 16 This application provides a timing diagram for an MCU3 timeout response to a data error. Figure 17 This is a timing diagram for a fault that MCU3 cannot display, as provided in this application. Combined with... Figures 11 to 17 The image transmission steps in the data packet sending process of this application include: a. Based on the trigger condition index, the animation to be displayed is read from the flash, i.e., the first animation (animation number, total number of animation frames, number of LEDs displayed in the MCU block corresponding to each frame, number of frames sent). b. The control command LSC_202command_request=0x01 is composed of the screen sending request (i.e., the first request), Animation_ID=current animation index number, Total_animation_picture=current total number of animation frames, current_animation_picture=current number of frames; Number_light_beads1 is the number of LEDs lit in the current frame MCU1, number_frame1 is the total number of LSC_101 frames of data that the current frame MCU1 needs to send; Number_light_beads2 is the number of LEDs lit in the current frame MCU2, number_frame2 is the total number of LSC_102 frames of data that the current frame MCU2 needs to send; Number_light_beads3 is the number of LEDs lit in the current frame MCU3, number_frame3 is the total number of LSC_103 frames of data that the current frame MCU3 needs to send. Meanwhile, LSC_201 LSC_state=0x01: Animation data is being sent; if it is the first 6 frames, LSC_control=0x00: Periodic screen refresh is not allowed; when preparing to send the 7th frame, LSC_control=0x01: Periodic screen refresh is allowed. LSC_101, LSC_102, and LSC_103 include the data frame sequence number of each image (ever_image_frame_serial), the total number of data frames for each image (ever_image_total_frame_number), whether the LED is displayed (Position_State1), and the LED display data (Position_Data1). Among them, `ever_image_frame_serial` (0x00 - 0xFF) represents the frame sequence number of each image's data frame. (LSC still needs to send data frames in the order of image data); `ever_image_total_frame_number` (0x00 - 0xFF) represents the total number of data frames for each image. (This byte only needs to be added when the value of the `ever_image_frame_serial` byte in the first frame of each image data frame is 0x00); `Position_State1` (bit 0) represents the state of LED 1. If it is 1, the brightness value of LED 1 follows; if it is 0, the state value of the second LED follows; `Position_Data1` (bits 1-5) represents the brightness value of LED 1. c. Wait for responses from the three nodes. If a timeout of 10ms occurs and no response is received from any of the following nodes: HALO_NOTE1_301 for MCU1, HALO_NOTE2_302 for MCU2, or HALO_NOTE3_303 for MCU3, or if a response is received but an error is reported (err_define != 0), the process must be retried 5 times. d. If all 5 attempts fail, report the corresponding HALO fault; Figure 13 As shown, the HALO_NOTE3_303 response for MCU3 failed. After retries 5 times, the fault was recorded and the screen went black. Figure 14 As shown, HALO_NOTE3_302 corresponding to MCU2 did not respond. After 5 retries, the fault was recorded and the screen was turned off. e. If all responses are received, and the response command is command_respond = 0x01 (i.e., the first response): ready to receive data, then proceed to the data packet sending process; f. If all responses are received, and any one of them contains a command_respond = 0x02: Not ready to receive new data, then after a 10ms delay, resend the above request b. If the timeout is 1 second and the response is still "Not ready," stop sending, send a screen-off command, exit, and return to a; Figure 15As shown, the HALO_NOTE3_303 response corresponding to MCU3 is not ready or does not meet the receiving requirements. After retrying the transmission request, if the response is not ready for 1 second, the transmission will stop and the screen will turn off. g. Data transmission process: The content is stored in flash and all data packets are continuously pushed according to the different IDs of the three nodes; LSC_101 corresponds to MCU1, LSC_102 corresponds to MCU2, and LSC_103 corresponds to MCU3. h. After the data segment is sent, send the control command LSC_202 command_request = 0x04 (i.e., the message indicating the completion of the first animation): Screen data transmission completed; Animation_ID = current animation index number, Total_animation_picture = total number of frames in the current animation, current_animation_picture = current screen number; Number_light_beads1: number of lit LEDs in the current screen MCU1, number_frame1: total number of LSC_101 frames of data that the current screen MCU1 needs to send; Number_light_beads2: number of lit LEDs in the current screen MCU2, number_frame2: total number of LSC_102 frames of data that the current screen MCU2 needs to send; Number_light_beads3: number of lit LEDs in the current screen MCU3, number_frame3: total number of LSC_103 frames of data that the current screen MCU3 needs to send; (The above data is the same as in step b). i. Wait for replies from 3 nodes. If a timeout of 10ms occurs and no one of HALO_NOTE1_301, HALO_NOTE2_302, or HALO_NOTE3_303 is received, or if a reply is received but an error is reported (err_define != 0), 5 retry attempts are required. j. If all responses are received, and the response command is command_respond = 0x03: the current screen is received correctly, then determine whether the animation screen has been sent completely. If sent completely, stop; otherwise, return to b to send the next screen. Figure 11 As shown, for a given image, the system responds with "Ready to receive" and "Received successfully," indicating "OK" (the second response). Then, the system sends the next image (the second animation). k. If all responses are received, and any one of them has command_respond = 0x04: current screen reception error, data frame ID error / 0x05: current received data error, data frame content error, then return to process b to retransmit the previously sent data; Figure 16As shown, MCU3 responded with a HALO_NOTE3_303 error, requesting a retry. 1. If all responses are received, and any one of them has command_respond = 0x06: the actuator has an internal fault and cannot control the output, then the process stops and the corresponding fault is reported; Figure 17 As shown, if the HALO_NOTE3_303 response corresponding to MCU3 cannot display the fault, then the process is stopped and the corresponding fault is recorded; m. After all screen displays are sent, LSC_control = 0x01 (allow periodic screen refresh) needs to be set, and then the screen should be sent 8 more times. After 8 times, select LSC_control = 0x00 (disallow periodic screen refresh) and send a screen-off command once before exiting. For example... Figure 12 As shown, after all images have been sent and the screen has been refreshed 8 times, the screen turns off after receiving the screen-off command.

[0084] Figure 18 This is a timing diagram of a normal control screen shutdown provided in this application; Figure 19 This application provides a timing diagram for an MCU3 responding to an error in a screen-off command. Figure 20 This is a timing diagram provided in this application for an MCU2 that fails to respond to a screen-off command after a timeout. Combined with... Figures 18 to 20 The screen-off process in the data packet sending process of this application includes the following steps: a. When the screen-off condition is met, send LSC_202 command_request = 0x08: screen-off control (i.e., the second request); c. Wait for replies from 3 nodes. If a timeout of 10ms occurs and no one of HALO_NOTE1_301, HALO_NOTE2_302, or HALO_NOTE3_303 is received, or if a reply is received but an error is reported (err_define != 0), 5 retry attempts are required. d. If all 5 attempts fail, report the corresponding HALO fault; Figure 19 As shown, if MCU3 responds with an error status after 5 screen-off requests, it records the fault; Figure 20 As shown, if MCU2 fails to respond to 5 screen-off requests, a fault is recorded. e. When the HALO screen turns off all displays, it receives 0x0a responses from three nodes: screen off has been controlled (i.e., third response); Figure 18 As shown, if MCU1, MCU2, and MCU3 all respond to the screen-off request by turning off the screen, then the screen will be turned off.

[0085] It should be noted that this application involves an interactive screen that uses three nodes (MCU1 / MCU2 / MCU3) to control the corresponding LEDs, such as... Figure 21 As shown, an animation is divided into 3 pages. The first and third pages contain 2804 LEDs, requiring one page for storage. The second page contains 4892 LEDs, requiring two pages for storage. Each page contains the following information: the animation number (address 0, 2 bytes), the total number of frames in the animation (address 2, 2 bytes), the current number of frames in the animation (address 4, 2 bytes), the number of LEDs to be lit in MCU1 (address 6, 2 bytes), the number of CANFD frames to be sent by MCU1 (address 8, 2 bytes), and the number of LEDs to be lit in this segment, the number of CANFD frames to be sent in this segment, the number of LEDs to be lit in this segment, and the number of CANFD frames to be sent in this segment (address 9).

[0086] The requirements for LED data arrangement include: each LED must have a 1-bit status bit; if the status bit is 0, it means it does not need to be lit; if the status bit is 1, it means it needs to be lit, and then a 5-bit lighting level data is required immediately following it; the data segments are dynamically combined and adjusted in real time according to the lighting requirements of the LEDs; information such as the animation number, the total number of frames in the animation, the current frame number in the animation, the number of LEDs to be lit in the segment, and the number of CANFD frames to be sent in the segment are sent through the LSC_202 control request. LED data XX is sent through data IDs LSC_101 / LSC_102 / LSC_103; when sending data IDs, they are sent sequentially. For example, if LSC_101 needs to send 30 frames of data, it is sent continuously, avoiding frame intervals as much as possible; after sending one page, the second page is sent, and then the third page.

[0087] Step B2: If the control signal is used to control the first lamp group, send a second message to the first lamp group; The second message is used to instruct the first light group to periodically adjust the color and brightness of each light to match the lighting effect data.

[0088] In some embodiments, the light controller supports music rhythm control based on data stored in a storage device.

[0089] In this embodiment of the application, for the second message, namely the lighting control command: When the lighting control is executed, the ambient light switch is on, and the switch status must be updated to AtmoLightAAEnable=1 in the control message; the lighting control command is sent with an 8ms cycle, and all changes to the color_LEDx and brightness_LEDx values ​​will be sent out with the cycle message (x is the LED number); the 6 nodes poll and send, and the maximum output synchronization will not exceed 8ms, which is allowed; For sending backlight level when the lights are off: the ambient light switch is on / off, and the switch status needs to be updated to AtmoLightAAEnable=0 in the control message, and the brightness of all lights is brightness_LEDx=0; the backlight level value BcmDimmerLvl sent by BCAN is sent to all lights periodically. For fault detection: all lights will return their internal status every 200ms; LSC records the internal status of the controller; when ERR_state!=0, an internal error is reported; the switch mounting box assembly (right) and the electric door lock / unlock switch assembly (left) negotiate not to report any faults; if no message is received from the node after 2 seconds, it is confirmed that the node is indeed lost, and a network fault status is reported.

[0090] In this embodiment, if it is a non-static mode lighting control command, the lighting control command is sent with a 20ms period. All values ​​of color change (ColorX_Setting) and brightness change (BrightnessX_setting) are sent out with the periodic message (x is the lamp number); the four LIN buses are refreshed synchronously. If it is a static mode lighting control command, the lighting control command is sent with a 200ms window switching. For example, within the 0-200ms window, the control command is output with a 20ms period. Within the 200-400ms window, no control command is output, and the data of the lamp node is polled; within the 400-600ms window, the control command is output again, and so on. In some embodiments, for fault detection: the BCM power switch is ON and the lighting control mode is static mode; the LSC will read the continuous fault status of the light node in a 200ms window (0-200ms lighting control, 200-400ms status acquisition, 400-600ms lighting control, 600-800ms status acquisition, and so on), and read the continuous fault status of the light node after 2s. If there is an error in bit 0 or bit 1 of the returned ERR_ST, an internal fault of the node is reported; if no message from the node is received after a 2s timeout, it is confirmed that the node is indeed lost, and a network fault status is reported.

[0091] In some embodiments, the method to be protected by this application further includes the following: The lamp controller detects the fault status of the first lamp group and the interactive display device; if fault information is detected, one or more of the following operations are performed: storing the fault information in the storage device; reporting the fault information.

[0092] This application monitors the malfunctions of ambient lighting and interactive screens, stores and reports malfunction information, and supports background monitoring and maintenance.

[0093] In this embodiment of the application, the data stored in the storage device includes one or more of the following: the data stored in the storage device includes one or more of the following: a first identifier of the lighting effect to be presented; the total number of images of the lighting effect to be presented; a second identifier of the current pre-presented image; the number of lights that need to be lit corresponding to the second identifier; and the number of controller local network frames that need to be sent at the flexible data rate corresponding to the second identifier.

[0094] In this embodiment of the application, if the data stored in the storage device is updated, and the update occurs before mass production, the data stored in the storage device is rewritten, and the starting address of each lighting effect data is re-identified.

[0095] In this embodiment of the application, if the data stored in the storage device is updated, and the update occurs after mass production, target data is written into the blank storage space of the storage device, and the starting address of the target data is identified; wherein, the blank storage area is a reserved area in the storage device and located in the last segment of the storage device.

[0096] In this embodiment of the application, if the storage block corresponding to the first data is a faulty block, the faulty block is identified, and the storage location corresponding to the first data is moved to the next position; the first data is the data to be stored in the storage device.

[0097] Figure 22 This is a flowchart of the update scheme provided in this application, such as... Figure 22 As shown, after the LSC is powered on, the diagnostic service is entered to confirm whether software flashing is required. If not, the application software is entered and then terminated. If yes, it is determined whether it is before or after mass production. If it is before mass production, all data in the flash is cleared; complete storage data is written, and the starting address of each lighting effect data is marked and remembered; initialization is performed, and the application software is entered again and then terminated. If it is after mass production, based on the existing data storage and memory, a blank flash storage area is identified, the newly added / modified target data is written, and the starting address is marked and remembered; initialization is performed, and the application software is entered again and then terminated.

[0098] It should be noted that, using the accompanying host computer, external flash data is updated via FBL; before mass production: the entire flash is updated using the host computer tool, clearing all stored data and rewriting it; after mass production: the target data is written into the blank storage space behind the flash; when bad blocks are encountered during the data transmission process, the bad block is marked, and the data of the bad block is moved to the next block.

[0099] The update requirements include: a. Reserve the custom space first - place it at the very end of the entire Flash file. b. Upgrade file includes address information c. Before mass production, any changes will erase the entire non-custom area and require all animation data to be rewritten from scratch. d. Before mass production, the data refresh may cause data address offset due to the size of the newly written data being different from the original, or bad block data being skipped during the new erasure process. Therefore, it is necessary to resynchronize the logical address and physical address mapping relationship after each refresh. e. The APP's logical lookup address must be synchronized with the updated file address. If there is a change, the APP will also need to be updated and upgraded. f. The data file needs to be converted to a hex file for the upgrade; g. Updates after mass production do not erase previous data, but only add new data. Therefore, the address of the upgrade file after SOP needs to avoid the previous valid data segment. Since the data is newly added, the corresponding APP logic program needs to be upgraded accordingly to be used. h. Flash upgrade files and MCU upgrade files are packaged separately; i. Custom space sections cannot be modified.

[0100] This application controls the screen lighting effects of over 10,000 LEDs using a low-power MCU and a low-speed CAN FD bus. The internal flash memory stores the lighting effect data, supporting data updates and replacements, and allowing for flexible adjustment of video data content. This application provides a computer device including a memory and a processor. The memory stores a computer program that can run on the processor. When the processor executes the program, it implements some or all of the steps in the above-described method.

[0101] This application provides a computer-readable storage medium storing a computer program thereon, which, when executed by a processor, implements some or all of the steps in the above-described method. The computer-readable storage medium can be transient or non-transient.

[0102] This application provides a computer program including computer-readable code. When the computer-readable code is run in a computer device, the processor in the computer device executes some or all of the steps in the above-described method.

[0103] This application provides a computer program product, which includes a non-transitory computer-readable storage medium storing a computer program. When the computer program is read and executed by a computer, it implements some or all of the steps in the above-described method. This computer program product can be implemented specifically through hardware, software, or a combination thereof. In some embodiments, the computer program product is specifically embodied as a computer storage medium; in other embodiments, the computer program product is specifically embodied as a software product, such as a software development kit (SDK), etc.

[0104] It should be noted that the descriptions of the various embodiments above tend to emphasize the differences between them, while their similarities or commonalities can be referred to interchangeably. The descriptions of the above embodiments of the device, storage medium, computer program, and computer program product are similar to the descriptions of the above method embodiments and have similar beneficial effects. For technical details not disclosed in the embodiments of the device, storage medium, computer program, and computer program product of this application, please refer to the descriptions of the method embodiments of this application for understanding.

[0105] Figure 23 This is a schematic diagram of a hardware entity of a vehicle in an embodiment of this application, such as... Figure 23 As shown, the hardware entity of the vehicle 2300 includes: a processor 2301, a communication interface 2302, and a memory 2303, wherein: The processor 2301 typically controls the overall operation of the vehicle 2300, which may be the control method for implementing the projection provided in the embodiments of this application, for example, such as... Figure 7 The method shown.

[0106] Communication interface 2302 enables computer devices to communicate with other terminals or servers via a network.

[0107] The memory 2303 is configured to store instructions and applications executable by the processor 2301, and can also cache data to be processed or already processed by the processor 2301 and various modules in the vehicle 2300 (e.g., image data, audio data, voice communication data, and video communication data). It can be implemented using flash memory or random access memory (RAM). Data transfer between the processor 2301, the communication interface 2302, and the memory 2303 can be performed via bus 2304.

[0108] This application provides a computer storage medium storing one or more programs that can be executed by one or more processors to implement the steps of the projection control method as described in any of the above embodiments.

[0109] It should be noted that the descriptions of the storage medium and device embodiments above are similar to those of the method embodiments above, and have similar beneficial effects. For technical details not disclosed in the storage medium and device embodiments of this application, please refer to the descriptions of the method embodiments of this application for understanding.

[0110] The aforementioned processor can be at least one of the following: Application Specific Integrated Circuit (ASIC), Digital Signal Processor (DSP), Digital Signal Processing Device (DSPD), Programmable Logic Device (PLD), Field Programmable Gate Array (FPGA), Central Processing Unit (CPU), Controller, Microcontroller, and Microprocessor. It is understood that other electronic devices can also implement the functions of the aforementioned processor, and this application does not specifically limit the specific implementation.

[0111] The aforementioned computer storage media / memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic random access memory (FRAM), flash memory, magnetic surface memory, optical disc, or compact disc read-only memory (CD-ROM), etc.; or it can be various terminals that include one or any combination of the above-mentioned memories, such as mobile phones, computers, tablet devices, personal digital assistants, etc.

[0112] It should be understood that the phrase "one embodiment" or "an embodiment" throughout the specification means that a specific feature, structure, or characteristic related to the embodiment is included in at least one embodiment of this application. Therefore, "in one embodiment" or "in an embodiment" appearing throughout the specification does not necessarily refer to the same embodiment. Furthermore, these specific features, structures, or characteristics can be combined in any suitable manner in one or more embodiments. It should be understood that in the various embodiments of this application, the sequence numbers of the above steps / processes do not imply a sequential order of execution; the execution order of each step / process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application. The sequence numbers of the above embodiments of this application are merely descriptive and do not represent the superiority or inferiority of the embodiments.

[0113] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element.

[0114] The above are merely embodiments of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application.

Claims

1. A vehicle headlight control method, characterized in that, Applied to a vehicle, the vehicle includes a lighting control system, the lighting control system comprising: a lamp controller, an interactive display device, a first lamp group, and a domain controller; the lamp controller is connected to the interactive display device, the first lamp group, and the domain controller, the method comprising: The light controller receives control signals sent by the domain controller. The lamp controller controls the display content of one or more of the interactive display devices and the first lamp group based on the control signal.

2. The method according to claim 1, characterized in that, The vehicle lighting control system further includes a storage device connected to the lighting controller and communicating with the lighting controller via an internal synchronous serial peripheral interface; controlling the display content of one or more of the interactive display device and the first lighting group based on the control signal includes: Retrieve lighting effect data that matches the control signal from the storage device; Based on the lighting effect data, control the display content of one or more of the interactive display device and the first light group.

3. The method according to claim 2, characterized in that, The step of controlling the display content of one or more of the interactive display device and the first light group based on the lighting effect data includes: If the control signal is used to control the interactive display device, a first message is sent to the interactive display device; wherein, the first message is used to obtain the status of the interactive display device; If the status of the display interaction device is successfully obtained and the status is fault-free, the first animation to be presented is read from the lighting effect data; Send a first request to the interactive display device; wherein the first request is used to request the transmission of the first animation; If a first response is received, and the first response indicates that the interactive display device is ready to receive the first animation, a message indicating that the first animation has been sent to the interactive display device is sent; If a second response is received, and the second response indicates that the display interaction device has successfully received the first animation, a request to transmit the second animation is sent to the interactive display device. When the interactive display device is ready to receive the second animation, the second animation is sent to the interactive display device until the interactive display device successfully receives or presents the lighting effect data. The lighting effect data includes the first animation and the second animation. The second animation is the data following the first animation.

4. The method according to claim 3, characterized in that, The first request also indicates that if the interactive display device is not allowed to refresh the screen during the sending of the first animation, the interactive display device is allowed to refresh the screen when sending the N+1th screen. The method further includes: If no first response is received, or if the first response indicates a malfunction of the interactive display device, or if the first response indicates that the interactive display device cannot receive the first animation, the first request is resent M times; where N and M are positive integers. Once the lighting effect data is presented, a second request is sent to the interactive display device via the lighting controller; wherein the second request is used to instruct the interactive display device to turn off the screen. The interactive display device turns off all displays on the screen and sends a third response to the light controller; the third response indicates that the interactive display device has successfully turned off the screen.

5. The method according to claim 2, characterized in that, The step of controlling the display content of one or more of the interactive display device and the first light group based on the lighting effect data includes: If the control signal is used to control the first light group, a second message is sent to the first light group; wherein, the second message is used to instruct the first light group to periodically adjust the color and brightness of each light to match the lighting effect data.

6. The method according to claim 2, characterized in that, The method further includes: The lamp controller is used to detect the fault status of the first lamp group and the interactive display device; If fault information is detected, perform one or more of the following operations: store the fault information in the storage device; report the fault information.

7. The method according to claim 2, characterized in that, The data stored in the storage device includes one or more of the following: a first identifier for the lighting effect to be presented; the total number of images of the lighting effect to be presented; a second identifier for the currently pre-presented image; and the number of lights that need to be lit corresponding to the second identifier. The second identifier corresponds to the number of controller local network frames that need to be sent at a flexible data rate; the method further includes: If the data stored in the storage device is updated before mass production, the data stored in the storage device is rewritten and the starting address of each lighting effect data is re-identified. If the data stored in the storage device is updated, and the update occurs after mass production, the target data is written into the blank storage space of the storage device, and the starting address of the target data is identified; wherein, the blank storage area is a reserved area in the storage device and located in the last segment of the storage device.

8. The method according to claim 2, characterized in that, The method further includes: If the storage block corresponding to the first data is a faulty block, the faulty block is identified, and the storage location corresponding to the first data is moved to the next position; the first data is the data to be stored in the storage device.

9. The method according to claim 1, characterized in that, The computing power of the lamp controller is lower than that of the domain controller; The lamp controller communicates with the first lamp group via a local interconnection network bus or a first flexible data rate controller local network bus. The lamp controller communicates with the interactive display device via a second flexible data rate controller local network bus. The lamp controller communicates with the domain controller via the controller local network bus or the third flexible data rate controller local network bus. Wherein, the communication rate corresponding to the local network bus of the first flexible data rate controller is less than the communication rate corresponding to the local network bus of the second flexible data rate controller; the communication rate corresponding to the local network bus of the first flexible data rate controller is equal to the communication rate corresponding to the local network bus of the third flexible data rate controller; and the communication rate corresponding to the local network bus of the controller is less than the communication rate corresponding to the local network bus of the first flexible data rate controller.

10. A vehicle, characterized in that, The vehicles include: Memory is used to store executable instructions or computer programs. The processor, when executing computer-executable instructions or computer programs stored in the memory, implements the vehicle lighting control method according to any one of claims 1 to 9.

Images