Multicolor LED built-in IC multicolor color linkage control system and method

Abstract

The invention discloses a multicolor LED built-in IC multicolor color linkage control system and a multicolor LED built-in IC multicolor color linkage control method, relates to the technical field of embedded control and communication driving of addressable multicolor LED pixel unit lamp strips or lamps, and is used for solving the problems that linkage multicolor is easy to jump and flicker at a hue boundary and the color consistency between pixel units is difficult to maintain for a long time. Resetting and enumerating the serially connected pixel units by the master control, loading channel gain, gamma and current calibration parameters, and establishing linkage object mapping and coupling weight; generating a target color on an HSV track according to a control period, and suppressing kick at a hue boundary through vector synthesis and weight gating; and then calibration quantization, frame sealing and protocol coding sending are completed, regional fantasy colors are achieved, and closed-loop calibration is carried out in combination with current or optical feedback.

Description

Technical Field

[0001] This invention relates to the field of embedded control and communication driving technology for addressable multi-color LED pixel unit light strips or lamps, and more specifically, to a multi-color LED built-in IC color linkage control system and method. Background Technology

[0002] With the increasing demand for addressable multi-color LED pixel units in landscape lighting, stage lighting, and consumer electronics, RGB or RGBW pixel units with built-in driver ICs are often connected in series to form a link, with the main control periodically sending data to achieve a color-changing effect. Existing solutions often use fixed weights for hue interpolation or direct numerical weighting, which can easily lead to abrupt changes in color near the endpoints of the hue cycle, such as flickering at the boundaries, breaks, and propagation along the linkage. Simultaneously, differences in luminous efficacy between pixel units, gamma nonlinearity, and constant current deviations can cause color inconsistencies, while temperature rise and aging can cause parameter drift. Furthermore, inconsistent link reset, enumeration addressing, and channel order or bit width configuration can easily lead to frame drops and latch asynchrony. Without current or optical feedback, the main control cannot correct these issues in time, affecting brightness, color accuracy, and long-term reliability. In addition, some solutions use simplified models to reduce computational load, making it difficult to balance smooth linkage and real-time performance, requiring higher performance.

[0003] To address the above problems, this invention proposes a solution. Summary of the Invention

[0004] In order to overcome the above-mentioned defects of the prior art, embodiments of the present invention provide a multi-color LED built-in IC color linkage control system and method to solve the problems mentioned in the background art.

[0005] To achieve the above objectives, the present invention provides the following technical solution: In a preferred embodiment, it includes: After the power supply is stable, the main controller sends a reset sequence to the pixel unit link, determines the logical address and number of the pixel unit link, and divides the pixel unit into multiple linkage objects according to the physical continuous interval, geometric position or user-configured grouping information recorded in the preset grouping table. It generates a mapping from each linkage object to a subset of pixel unit addresses and establishes a coupling weight matrix between linkage objects according to adjacency, distance attenuation or group priority rules. In each control cycle, the main controller samples the hue function, saturation function, and brightness function, rewrites the hue as a two-dimensional vector composed of cosine and sine, and constructs the brightness visibility coefficient, boundary critical coefficient, traction consistency index, and cycle change steepness coefficient. Based on this, the coupling weight matrix is ​​reorganized and limited row by row in cycle to obtain the reorganized weight. The hue vectors of the target linkage object itself and its adjacent linkage objects are weighted and summed according to the reorganized weight to obtain the candidate synthesis vector. Then, the gate coefficient is mixed and normalized, and the time continuous coefficient is recursively fused to obtain smooth hue, saturation, and brightness. After being converted into red, green, and blue components, they are expanded into a set of pixel unit-level input components by mapping the pixel unit address subset. The main controller encapsulates the set of pixel-level input components into a driving frame spliced ​​from pixel-level data segments and sends it to the pixel-level link; After the drive frame is sent and the built-in chip latch timing is met, the main controller triggers a synchronous update, collects and normalizes the feedback quantity, constructs the target brightness quantity or the target color ratio quantity, calculates the brightness error or the color ratio error, and recursively updates the calibration parameters according to the update step size and limits the amplitude.

[0006] In a preferred embodiment, after the power supply is stable, the main controller sends a reset sequence to the pixel unit link to clear the residual state. Then, it determines the logical address and quantity of each pixel unit by address writing recursion or enumeration in cascade order, and establishes the correspondence between the pixel unit index and the physical location.

[0007] In a preferred embodiment, after obtaining the logical address, the main controller loads and writes color channel gain parameters, nonlinear mapping parameters, and constant current calibration parameters (writable in registers or calculated on the main control side, depending on whether the built-in chip supports corresponding registers) pixel by pixel. Then, it reads a preset grouping table, which records at least the correspondence between the logical address of each pixel unit and the identifier of the linked object, or records physical continuous intervals, geometric location regions, or user-configured grouping rules. Based on the grouping table, the main controller groups pixel units with the same linked object identifier or satisfying the same grouping rule into the same linked object, thereby dividing the pixel unit into multiple linked objects and generating a corresponding pixel unit address subset mapping for each linked object. Simultaneously, it generates a coupling weight matrix between linked objects based on the topological adjacency relationship, geometric distance attenuation relationship, or group priority rule between linked objects.

[0008] In a preferred embodiment, the main controller calculates the target color vector and target brightness scalar for each linked object in each control cycle, and expands the linked object-level results into pixel-level color components according to the mapping from object to pixel unit. The main controller adopts a unified parameterization method for hue, saturation, and brightness, establishes a hue function, saturation function, and brightness function for each linked object, and uses the control cycle number and the mapping from the control cycle to the equivalent time as independent variables. The main controller generates a basic hue by linearly advancing the modulo operation or by advancing the hue lookup table, and then determines the phase offset based on the linked object number, geometric position, or user configuration, and performs translation and modulo operation on the basic hue to obtain the offset hue. Simultaneously, fixed values ​​of saturation and brightness are read from the mode parameter table or user configuration, or saturation and brightness that change over time are generated according to a preset waveform function; after obtaining the trajectory parameters of each linked object, the main controller applies the coupling weight matrix to the parameters or their equivalent vector representation.

[0009] In a preferred embodiment, after sampling the hue function, saturation function, and brightness function of each linked object in each control cycle, the main controller rewrites the hue from a scalar into a two-dimensional vector composed of cosine and sine. It then obtains the brightness visibility coefficient by multiplying saturation and brightness, the boundary critical coefficient by the minimum distance from the hue to the cycle endpoint, the relative direction quantity by the dot product of the current hue vector and each adjacent hue vector, and calculates the traction consistency index in conjunction with the coupling weights. Finally, it obtains the cycle change steepness coefficient by the dot product of the current and previous cycle hue vectors. Based on the above multi-factor judgment quantities, the main controller reorganizes and limits the coupling weight matrix row by row on a cycle-by-cycle basis: constructing a confidence factor for each adjacent object according to the relative direction quantity; constructing a boundary-oriented suppression factor for the target object according to the boundary critical coefficient, brightness visibility coefficient, and change steepness coefficient; and using the suppression factor to interpolate between the original coupling weight contribution and the self-holding ratio to generate reorganized weights. Finally, it nonnegates and normalizes the reorganized weights and gives a degenerate assignment when the denominator is zero.

[0010] In a preferred embodiment, under the reshaping weight, the main controller multiplies the hue vector of the target linked object itself and the hue vectors of each adjacent linked object with which it is coupled by the corresponding reshaping weight, and then performs a weighted summation to obtain a candidate composite vector. The amplitude of the candidate composite vector is calculated, and then a gating coefficient is constructed according to the amplitude. The candidate composite vector is mixed with the hue vector of the target object itself according to the gating coefficient and normalized to obtain a gated composite vector. Then, the linked composite hue is inversely calculated by the four-quadrant arctangent and modulo normalization. The main controller uses the same reshaping weight as the hue to perform consistent weighted synthesis of saturation and brightness and performs range truncation. The main controller derives a time continuity coefficient from the boundary critical coefficient, brightness visibility coefficient and change steepness coefficient. According to the coefficient, the current period gated composite vector and saturation, brightness and smoothing amount of the previous period are recursively fused and the smoothed hue vector is normalized. Then, the smoothed hue is inversely calculated.

[0011] In a preferred embodiment, the master controller saves the gating synthesis vector of the previous cycle and calculates the directional consistency with the candidate synthesis vector of the current cycle. When the consistency is low and the boundary is critical and the visibility is at a high level, the gating coefficient is lowered according to a fixed rule to make the synthesis vector back towards the direction of the target object itself or the synthesis direction of the previous cycle. After obtaining the smooth hue, saturation and brightness of each linked object, the master controller completes the calculation of hue, saturation and brightness to red, green and blue components according to the standard piecewise formula. When the white light channel is enabled, the white light component is extracted according to the minimum components of the three colors, and white light stripping is performed on red, green and blue to obtain the stripped three color components. The master controller then expands the object-level color components to the pixel unit-level channel input components according to the mapping of the linked object to the pixel unit address subset. During the expansion, the phase offset within the pixel unit can be introduced to replace the smooth hue before performing color component conversion. Finally, the pixel unit index and each channel input component are written to the frame buffer.

[0012] In a preferred embodiment, the main controller determines the structure of the driving frame, which consists of multiple pixel unit data segments concatenated sequentially, based on the pixel unit link cascading order, and determines the arrangement of each pixel unit data segment according to the mapping from logical address to cascading order. For each pixel unit, the main controller reads the channel gain parameter from the running table, multiplies the pixel unit-level input component by the channel gain and truncates it, then reads the gamma parameter or a lookup table to perform a nonlinear mapping on the truncated component to obtain the driving code domain value. It also reads the current calibration coefficient and the reference constant current value to calculate the current constraint scaling factor, scales the driving code domain value proportionally, and truncates the driving code range. The main controller rounds the scaled driving code domain value. The quantization process involves quantizing or introducing pseudo-random numbers or error diffusion to generate quantization jitter terms, resulting in integer drive codes. Subsequently, each channel's integer drive code is encapsulated into pixel unit data segments according to the channel order configuration and concatenated in a cascaded order to form the drive frame payload. Cyclic redundancy check or checksum fields are then appended to the frame header or tail according to the configuration. The main controller maps the drive frame bit sequence into line timing signals according to the selected physical layer protocol and sends them. The single-line protocol uses pulse width ratio mapping and is output by a timer, direct memory access, or dedicated peripheral. The dual-line protocol outputs data synchronously according to the clock edge and outputs the clock and data by a serial peripheral. At the end of the frame, a low-level hold or frame synchronization control signal is output according to the latch time condition.

[0013] In a preferred embodiment, the main controller, based on the control cycle boundary, triggers a synchronous update after the end of the current cycle's drive frame transmission and the built-in chip latching timing is met. It then determines the latching conditions according to the low-level hold time of the single-wire protocol or the frame end marker, chip select signal, and setup hold time of the two-wire protocol. After latching, the main controller selects the feedback source according to the configuration and collects current sampling, optical brightness, or red-green-blue measurement quantities within a preset sampling window. Alternatively, it calculates the temperature drift prediction ratio based on a temperature and current model and normalizes the feedback quantity based on the extinguishing baseline and the reference drive frame measurement value. The main controller constructs a system based on the drive code and running table reference parameters already transmitted in the current cycle. The target brightness or color ratio is calculated based on the feedback type, and the brightness error or color ratio error is calculated accordingly. The main controller performs proportional recursion and amplitude limiting on the current calibration coefficient according to the update step size. When color feedback is available, the channel gain is recursively calculated and amplitude limited according to the channel error component. When the gamma parameter or lookup table meets the stability condition or is in the calibration frame, low-frequency recursion or proportional adjustment and amplitude limiting are performed. The main controller selects whether the updated parameters support online writing and sends them to the frame and performs readback or verification comparison, or writes them to the running table for the next cycle. When feedback quantity exceeds the limit, changes abruptly, or acquisition fails, the main controller stops the recursion according to the configuration or backtracks according to the amplitude limiting boundary and records the abnormal flag.

[0014] In a preferred embodiment, the module includes: an initialization pixel unit consistency configuration module, a color calculation module for color linkage, a drive frame generation encoding and sending module, a synchronous update calibration closed-loop module, and signal connections between the modules. The initialization pixel unit consistency configuration module is used by the main controller to send a reset sequence to the pixel unit link after the power supply is stable, determine the logical address and number of pixel unit links, divide the pixel unit into multiple linkage objects according to the physical continuous interval, geometric position or user-configured grouping information recorded in the preset grouping table, generate a mapping from each linkage object to the pixel unit address subset, and establish a coupling weight matrix between linkage objects according to the adjacency relationship, distance attenuation or same group priority rules. The color calculation module of the holographic linkage is used by the main controller to sample the hue function, saturation function, and brightness function in each control cycle. The hue is rewritten as a two-dimensional vector composed of cosine and sine, and the brightness visibility coefficient, boundary critical coefficient, traction consistency index, and cycle change steepness coefficient are constructed. Based on this, the coupling weight matrix is ​​reorganized and limited row by row in cycle to obtain the reorganized weight. The hue vectors of the target linkage object and its adjacent linkage objects are weighted and summed according to the reorganized weight to obtain the candidate synthesis vector. Then, the gate coefficient is mixed and normalized, and the time continuous coefficient is recursively fused to obtain smooth hue, saturation, and brightness. After being converted into red, green and blue components, they are expanded into a set of pixel unit-level input components by mapping the pixel unit address subset. The drive frame generation, encoding, and sending module is used by the main controller to encapsulate the set of pixel unit-level input components into a drive frame spliced ​​from pixel unit data segments and send it to the pixel unit link; The synchronous update calibration closed-loop module is used by the main controller to trigger synchronous update after the drive frame is sent and the built-in chip latch timing is met. It collects feedback quantities and normalizes them, constructs brightness target quantities or color ratio target quantities, calculates brightness errors or color ratio errors, and recursively updates calibration parameters according to the update step size and limits the amplitude.

[0015] The technical effects and advantages of the multi-color LED built-in IC color linkage control system and method of this invention are as follows: This invention organizes pixel units through linkage objects and coupling matrices, enabling unified scheduling of irregularly shaped stitching. During the hue synthesis stage, it introduces boundary criticality, traction consistency, and periodic variation judgment quantities to reorganize, gate, and self-hold weights, improving hue continuity across periods and significantly suppressing flicker and tearing. Combined with pixel-by-pixel unit gain, gamma, or current calibration and optional current or optical feedback recursive updates, it maintains consistent brightness and color accuracy over the long term. It also supports single-line or dual-line encoding, facilitating engineering implementation and expansion. Furthermore, it provides frame verification and anomaly feedback limiting strategies to reduce transmission and overcurrent risks, resulting in greater stability. Attached Figure Description

[0016] Figure 1 This is a schematic diagram of the transmission timing of the multi-color LED built-in IC color linkage control system and method of the present invention.

[0017] Figure 2 This is a comparison diagram of the hue boundary continuity of the multi-color LED built-in IC color linkage control system and method of the present invention.

[0018] Figure 3 This is a comparison chart of flicker performance indicators for the multi-color LED built-in IC color linkage control system and method of the present invention. Detailed Implementation

[0019] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0020] In this embodiment, the present invention discloses a multi-color LED built-in IC color linkage control method, including: Step 1: After the power supply is stable, the main controller sends a reset sequence to the pixel unit link, determines the logical address and number of pixel unit links, and divides the pixel unit into multiple linkage objects according to the physical continuous interval, geometric position or user-configured grouping information recorded in the preset grouping table. It generates a mapping from each linkage object to a subset of pixel unit addresses and establishes a coupling weight matrix between linkage objects according to adjacency, distance attenuation or group priority rules. Step 2: In each control cycle, the main controller samples the hue function, saturation function, and brightness function, rewrites the hue as a two-dimensional vector composed of cosine and sine, and constructs the brightness visibility coefficient, boundary critical coefficient, traction consistency index, and cycle change steepness coefficient. Based on this, the coupling weight matrix is ​​reorganized and limited row by row in cycle to obtain the reorganized weight. The hue vectors of the target linkage object itself and its adjacent linkage objects are weighted and summed according to the reorganized weight to obtain the candidate synthesis vector. Then, the gate coefficient is mixed and normalized, and the time continuous coefficient is recursively fused to obtain smooth hue, saturation, and brightness. After being converted into red, green, and blue components, they are expanded into a set of pixel unit-level input components by mapping the pixel unit address subset. Step 3: The main controller encapsulates the set of pixel unit-level input components into a driving frame spliced ​​from pixel unit data segments and sends it to the pixel unit link; Step 4: After the main controller finishes sending the drive frame and meets the built-in chip latch timing, it triggers a synchronous update, collects and normalizes the feedback quantity, constructs the target brightness quantity or the target color ratio quantity, calculates the brightness error or the color ratio error, and recursively updates the calibration parameters according to the update step size and limits the amplitude.

[0021] In step one, the main controller performs reset, enumeration, parameter loading, and parameter writing on the pixel unit link formed by multiple multi-color LED pixel units connected in series, so that the built-in IC of each pixel unit is in a working state that can receive control data and output constant current drive according to the set parameters. The pixel unit is a combination of a light-emitting device containing at least red, green, and blue light-emitting channels and a corresponding built-in IC; when the pixel unit contains a white light channel, the pixel unit further contains a white light-emitting channel. The built-in IC is used to parse the serially input control data into channel drive quantities and output the drive current of the corresponding channel according to the built-in constant current drive circuit.

[0022] After detecting that the power supply has reached and stabilized at the built-in IC power-on threshold, the main controller sends a reset sequence to the pixel unit link to eliminate any residual state in the link. The specific form of the reset sequence is determined by the physical transmission protocol used by the pixel unit link: when using a single-wire pulse width encoding protocol, the reset sequence can be a signal with a continuous low-level hold time not less than the built-in IC reset hold time; when using a dual-wire clock or data protocol, the reset sequence can be a preset reset frame or reset codeword sent under clock validity conditions. The main controller generates the reset sequence based on the reset conditions given in the built-in IC specifications or on reset conditions verified by actual testing; when using the latter, the main controller determines the reset sequence that can bring all pixel units to their initial state through repeated power-on tests during production testing or debugging and then embeds it into firmware parameters.

[0023] like Figure 1 As shown, after the reset is completed, the main controller performs pixel unit enumeration and address determination to obtain the logical address set of each pixel unit in the pixel unit link. The logical address is used to establish a one-to-one correspondence between pixel unit indices and physical locations within the main controller, and to determine the data segment corresponding to each pixel unit when sending control data. Pixel unit enumeration and address determination include the following two implementation methods, and the main controller must use at least one of them, selected as a configuration item in the main controller firmware: Firstly, when the built-in IC supports a writable address register or automatic addressing mode, the master controller sends an address write control frame to the link, causing the pixel unit links to sequentially obtain different addresses from the beginning to the end of the link in a cascading order. Specifically, the master controller writes the starting address at the beginning of the link and triggers an address recursion mechanism; this address recursion mechanism can be a hardware mechanism where the address increments by one for each pixel unit, or a cascading write mechanism where each pixel unit latches its own address and forwards the write frame to the next level. After the write is complete, the master controller obtains the address set: ; in, This represents the logical address of the j-th pixel unit, and N represents the number of pixel units. The address sequence written by the master controller is directly determined, so its source is the content of the address write frame.

[0024] Secondly, when the built-in IC does not support address registers and only supports cascading methods of data shifting and latching, the main controller defines the sequential position of the pixel unit in the link as the logical address. Specifically, the main controller determines the number N of pixel units by continuously sending control frames of a fixed format and observing the link response characteristics. The response characteristics include at least: a link end readback signal, a power supply current step characteristic, or a lighting response from external optical sampling. For example, in production testing, a single-pixel unit white light lighting scanning method can be used: the main controller sequentially writes a lighting value only to a certain data segment and writes an extinguishing value to the remaining data segments. The number of times the lighting response is detected by the optical sensor is used to obtain N. In this method, the logical address set is defined as: ; The address value is the pixel unit number, which is derived from the sequential number obtained through enumeration. The main controller will set the N and Write the pixel unit table to the master controller. The pixel unit table includes at least the following: logical address field, link order field, and calibration parameter index field corresponding to the pixel unit.

[0025] After obtaining the set of logical addresses, the master controller loads and sets channel consistency-related parameters to ensure that different pixel units present consistent color ratios and brightness outputs under the same control input. Channel consistency-related parameters include at least channel gain parameters, nonlinear mapping parameters, and current calibration parameters. The master controller determines the source of these parameter values ​​for each pixel unit and writes them into the built-in IC or stores them in the master controller's pixel unit table.

[0026] First, the master controller determines the channel gain vector for each pixel unit. The channel gain vector is used to proportionally correct the control components of each color channel, ensuring that the relative light intensity of each pixel unit meets a preset consistency standard. The master controller establishes the channel gain vector for pixel unit p: ; When a white light channel exists, it expands to .in, , , These represent the gain coefficients of each channel in pixel unit p. The source of these gain coefficients includes at least one of the following three, which the main controller explicitly selects and records during implementation: First, from the factory calibration table, where the relative light intensity of each channel in each pixel unit under the same driving code is measured using standard optical measurement equipment on the production line, and the gain coefficients are calculated and written to non-volatile memory, which the main controller reads after power-on; second, from online calibration, where the main controller measures the response of each channel using an external optical sensor on-site and calculates the gain coefficients in real time, storing them in the main controller's writable memory; third, from preset configuration, where typical gain coefficients from the same batch are used without individual calibration, and these coefficients are obtained through sampling calibration statistics and fixed in the firmware. The main controller will... There are two types of writing methods: when the built-in IC provides gain or color correction registers, the main controller will... The quantization is performed into a code value allowed by the register and written to the corresponding register; when the built-in IC does not provide the above registers, the main controller will calculate the channel control component. The coefficients are used as multiplicative coefficients in the calculation and are stored in the calibration field of the master pixel unit table.

[0027] Secondly, the main controller determines the nonlinear mapping parameters for each pixel unit, which are used to map the input channel control components into driving codes, so that the output brightness changes with the input to meet a preset visual or physical linear relationship. The main controller establishes gamma parameters for pixel unit p. Or create a lookup table When using gamma parameters, the main controller calculates the driver code according to the following mapping relationship: ; Where 'c' represents the channel identifier; This represents the input component value of pixel unit p in channel c; Input component full scale; Let p be the gamma parameter of the pixel unit. Full scale for the driver code; Write the driver code value for the built-in IC or frame encapsulation to channel c. Gamma parameter. The sources also include at least one of the following three methods: factory calibration fitting, online fitting, or preset typical values; when calibration fitting is used, the fitting data is obtained from the measurement pair of input component and output light intensity, and the main control or calibration tool performs power function fitting on the measurement curve to obtain the data. When a lookup table is used, the mapping relationship is as follows: ; in, This is a discrete mapping table, sourced from factory-generated discrete sampling, online discrete sampling, or a preset mapping table. The main controller's writing methods are also divided into two categories: when the built-in IC supports curve registers or table lookup mode, the main controller will... or Write to the built-in IC; when the built-in IC does not support it, the main controller completes this on the main controller side before generating the driver frame. The calculation is performed, and the result is encapsulated into the transmission frame.

[0028] Next, the main controller determines the current calibration parameters for each pixel unit, ensuring that the constant current output corresponding to the same driving code satisfies consistency constraints among pixel units and that the output does not exceed the allowable current limit. The main controller establishes current calibration coefficients for pixel unit p. The target value of the constant current in the channel is characterized by the following relationship: ; in, The reference constant current value for channel c is derived from the reference current level specified in the built-in IC specification or from a reference value given in the configuration file. The current calibration coefficients can be derived from at least: factory current sampling calibration, online current sampling calibration, or preset typical coefficients. and The meaning is the same as before. If the built-in IC uses a constant current range code to set the current, the main controller will... Mapped to a gear code and written to the constant current register; if the built-in IC does not provide a current register but only accepts drive codes, the main controller limits... The upper limit or by scaling the input components Achieve equivalent current constraint, and It is stored as a scaling parameter in the master pixel unit table.

[0029] After completing the loading and writing of the pixel-by-pixel calibration parameters, the main controller establishes a set of linkage objects and generates a mapping from objects to a set of pixel unit addresses, so that the same linkage operation can be applied to a group of pixel unit addresses simultaneously. The main controller constructs the set of linkage objects. Each linked object Corresponding to a subset of pixel unit addresses The controller represents this relationship as a mapping function: ; in, The generation methods include at least: grouping by physically continuous intervals, grouping by geometric location, or grouping by user configuration. Regardless of the generation method used, the master controller provides the grouping information in the form of a configuration file or a grouping table. The source, and Write it into the runtime context to make it a reusable mapping.

[0030] The master controller simultaneously generates a coupling weight matrix between linked objects, used to quantify the influence of one linked object on another. Master controller setup: ; in, Represents the linked object The coupling weight between the linked object i and the object i. The weights are generated based on at least one of the following rules, explicitly defined by the main controller: Based on topological adjacency rules: adjacency relationships are determined by the object grouping table; adjacent objects have higher weights, and non-adjacent objects have lower weights; Based on distance decay rules: object positions are given by the geometric position table, and weights are calculated using a distance function, the form of which is given in the embodiment; Based on same-group priority rules: objects within the same linkage group have higher weights, and objects across groups have lower weights. The main controller will generate... Stored in the runtime context, and for each Record its generation rule identifier so that the same weight matrix can be reproduced under the same configuration input.

[0031] Finally, the main controller organizes the key set and parameters obtained in step one into a pixel unit operation table and stores it in a fixed format. The pixel unit operation table includes at least: a set of pixel unit addresses. , Set of calibration parameters per pixel unit, Set of linked objects Mapping function The corresponding grouping table and coupling weight matrix The location where the main controller stores the pixel unit operation table is selected from the main controller's non-volatile memory or RAM depending on the implementation; when stored in RAM, the main controller reloads and rebuilds the pixel unit operation table from the non-volatile memory or external configuration file each time it is powered on.

[0032] In step two, the main controller calculates the target color vector and target brightness scalar for each linked object within each control cycle, and expands the target results at the linked object level into target color component values ​​at the pixel unit level, providing input for subsequent drive frame generation. To ensure that color calculation has a reproducible mathematical definition, the main controller adopts a unified color parameterization method in step two, representing the dynamic color rendering process as a function of color trajectory parameters and time progression parameters, and representing the mutual influence between linked objects as a combination operation involving coupling weight matrices.

[0033] First, define the color trajectory parameters. These parameters describe the pattern of color change over time in the iridescent effect. The main controller is for each linked object. Establish a set of color trajectory parameters: ; in, For hue function, It is a saturation function. The hue, saturation, and lightness are defined using a hue, saturation, and lightness color model. The selection of this color model is based on its ability to express continuous color variations with a single hue parameter and to facilitate periodic evolution. To avoid insufficient disclosure, the main controller must specify the hue, saturation, and lightness parameters during implementation. The source is determined, and the source includes at least: a preset mode parameter table, user configuration input, or configuration issued by the host computer; the main controller stores the source in the form of a mode identifier in the running context, and reads the corresponding parameter table item or configuration item through the mode identifier each time calculation.

[0034] To ensure that the hue, saturation, and brightness functions have clearly defined calculation rules, the main controller represents the time advancement parameters as a control cycle count or an equivalent timestamp. The main controller defines the control cycle sequence number kkk and the mapping from the control cycle to the equivalent time: ; in, At the starting time, To control the cycle; The time recorded by the main controller after the reset is completed in step one is given. The configuration is given by the timer settings or communication refresh settings of the main controller, and its source is either firmware configuration or user configuration. The main controller uses t as... The independent variable ensures time consistency calculation. If the implementation does not use real time but only the cycle number, the main controller will equivalently replace t with k while maintaining the consistency of the function form, thereby ensuring the reproducibility of the calculation.

[0035] The master controller then constructs a basic hue progression function for each linked object to generate continuously changing iridescent hues. The master controller selects at least one hue progression method and fixes the parameter source for the selected method to either a mode parameter table or user-configured input. Two implementable and interchangeable hue progression function forms are given, and the master controller must use at least one of them: When using a linear progression and modulus method, the main controller calculates the basic hue using the following formula: ; in, For linkage objects The basic hue, The initial hue, For hue angular velocity, This is a modulo normalization function used to constrain hue values ​​within a one-period range. The initial hue... The source is either a mode parameter table or user configuration input, and the hue angular velocity... The source is the mode parameter table or user configuration input, and it is stored by the main controller in floating-point or fixed-point form; the modulo normalization function The implementation method is to perform a modulo operation or a piecewise subtraction operation on the hue period. For example, the hue period can be set to a normalized period of 1 or an angle period of 360 degrees. The specific period unit is selected by the implementation and unified in the firmware.

[0036] When using a lookup table approach, the main controller calculates the basic hue using the following formula: ; in, This is a hue lookup table function. The hue change cycle is defined as follows. The hue lookup table is sourced from a mode parameter table or a firmware-built-in lookup table. The parameters are provided by the mode parameter table or user configuration input. The main controller implements non-linear or custom hue change trajectories through lookup tables, such as trajectories that start fast and then slow down or have multiple gradual changes.

[0037] After obtaining the basic hue, the main controller introduces a phase offset for each linked object to achieve staggered evolution of different linked objects on the same color trajectory. The phase offset is defined as follows: Its source is the linkage object mapping relationship and preset offset rules established in step one. The main controller determines according to one of the following rules. The rules are as follows: Based on the linkage object's sequence number, the main controller assigns a fixed sequence number to each linkage object and calculates the offset according to the sequence number; based on the linkage object's geometric position, the main controller calculates the offset according to the linkage object's position table; based on user configuration, the main controller directly reads the user-configured offset. To ensure the offset has a clear effect, the main controller uses the offset for hue or time parameter translation, and obtains the offset hue function using the following formula: ; in, For linkage objects The offset hue. Units and The hue period units used are consistent, and the main controller unifies them into the same unit in the firmware to avoid mixing.

[0038] In step two, the main controller also determines the saturation function and the brightness function. (Saturation function) Used to control the purity of color, lightness function Used to control the overall brightness of colors. For full disclosure, the main controller provides at least two types of sources: fixed value sources and time-varying sources. Fixed value sources refer to reading saturation and brightness constants from the mode parameter table or user configuration input; time-varying sources refer to generating saturation and brightness that change over time according to a preset waveform function. Taking brightness changing over time as an example, the main controller can use a breathing waveform function: ; in, Minimum brightness, For maximum brightness, The brightness variation period is defined by the parameters mentioned above, which are derived from the mode parameter table or user-configured input. The main controller uses a cosine function because its first derivative is continuous at the endpoints of the period, producing a continuous and smooth brightness variation. When the implementation does not support cosine calculation, the main controller uses a lookup table. The lookup table is stored in the firmware to keep the function definition unchanged.

[0039] After obtaining the color trajectory parameters of each linked object Then, the main controller performs linkage coupling calculations, and sets the coupling weight matrix... This is applied to color trajectory parameters or their equivalent vector representation to achieve color and brightness correlation changes between linked objects. This is to avoid hue discontinuity across periods caused by direct linear superposition in the HSV space; It should be noted that in the multi-color LED pixel unit link with irregular splicing, the main controller divides the pixel unit into multiple linked objects and generates hue functions for each. Saturation function With lightness function Simultaneously through the coupling weight matrix This causes multiple adjacent linked objects to have an overlapping effect on the same target linked object; because hue is a periodic surround quantity and each linked object introduces a different phase offset. Within certain control cycles, a clustering phenomenon occurs where the visual endpoints are the same color but the numerical values ​​cross boundaries: the hues of multiple adjacent linked objects appear to be close to the same color end, but numerically they are distributed at opposite ends of the hue cycle. Furthermore, due to the combined effects of control cycle progression, phase misalignment, and changes in saturation and brightness, the pulling direction of adjacent objects on the target linked object exhibits parallel, jump, and short-term reversal within adjacent cycles. At this time, even if the influence of a certain adjacent object on the target linked object is temporarily dominant within a certain cycle, it may only be a pseudo-advantage caused by phase progression across boundaries or changes in brightness and saturation. Once the synthesis direction is determined based on this, the hue progression of the target linked object will be pulled into the wrong cycle range, thus forming a sudden jump in adjacent cycles and amplifying it into a visible boundary flicker, break, or tearing sensation. Moreover, this anomaly will propagate along the coupling relationship to surrounding linked objects, forming a chain of visual instability.

[0040] Therefore, in this embodiment, as Figure 2 As shown, the main controller receives information from each linked object. Hue function Saturation function Brightness function Subsequently, instead of directly applying conventional weighting or interpolation to the hue values, the process is performed on each linked object... Construct decision variables related to the control cycle, and adjust the coupling weight matrix accordingly. The process involves rebalancing and limiting within a cycle, followed by hue synthesis and continuity processing on the rebalanced weights. This ensures that the hue remains continuous near the boundary of the hue cycle and suppresses sudden jumps caused by traction reversals in adjacent control cycles.

[0041] The main controller in the kth control cycle Indicate the calculation time, and for each linked object Construct a hue vector representation: ; in, For linkage objects At any moment The hue vector; when hue is expressed in angular units, the main controller will... Replace the angle-to-radian conversion result and fix the conversion rules in the firmware to ensure unit consistency. The main controller synchronously constructs the brightness visibility coefficient: ; in, It is obtained by directly multiplying the saturation function and the brightness function. Its purpose is to reduce the influence of hue perturbation on the judgment quantity under low saturation or low brightness, while increasing the influence of hue perturbation on the judgment quantity under high saturation and high brightness. To suppress abrupt jumps in values ​​across boundaries due to the same color at boundary endpoints, the main controller constructs a boundary critical coefficient based on the hue periodic boundary. The main controller selects the normalized periodic representation of hue in the firmware, enabling... When using angle representation, the main controller first divides the angle hue by the period angle to obtain the normalized hue before participating in subsequent calculations. The main controller defines the distance to the nearest period endpoint: ; And define the boundary critical coefficients: ; in, The boundary determination threshold is derived from the mode parameter table or user configuration input, and the main controller solidifies it as a threshold under normalized hue units. This is a truncation function. The above... exist The value approaches 1 when it is near the end of the cycle, and approaches 0 when it is far from the end. The main controller constructs an adjacency traction consistency coefficient to characterize the states of parallel, abrupt, and short-term reverse traction directions of multiple highly coupled adjacent objects. This applies to the target linked objects. The main controller manages all its adjacent linked objects. Calculate the relative direction cosine: ; in For vector dot product operation, The range of values ​​for is determined by the dot product property and is used to characterize the consistency of the angle between hue vectors. The main controller further calculates the weighted consistency index: ; Where the denominator is the weight normalization factor; when At that time, the main controller will Defined as 1 to indicate no adjacent traction. Because When adjacent hues are close in direction, the hue approaches 1; when they are opposite in direction, the hue approaches -1. Therefore... It can be used to characterize whether adjacent traction is consistent under the influence of weights.

[0042] To suppress sudden jumps caused by traction reversals in adjacent control cycles, the master controller constructs a steepness coefficient for cycle changes. The master controller stores the hue vector from the previous control cycle. and define: ; in, Used to characterize the magnitude of hue direction change between adjacent periods; the smaller the dot product, the greater the change. When k=0, the main controller will... Initialize to ,make .

[0043] The main controller constructs a weighting rebalancing factor based on the aforementioned coefficients and applies it to the target linkage object. The corresponding weighted rows undergo periodic reorganization. The master controller first constructs an adjacency confidence factor for each adjacent linked object i: ; in, The factor approaches 1 when adjacent directions are aligned and approaches 0 when directions are opposed, used to reduce the contribution of the adjacent object to the synthesis result when opposing traction directions occur. The master controller reconstructs the boundary-oriented suppression factor: ; in, The suppression coefficient is derived from the mode parameter table or user configuration input. This is the lower limit coefficient, sourced from firmware presets or user configuration input, used to prevent the inhibition factor from dropping to zero, thus halting the synthesis process; the above The weighting decreases when critical boundaries, high visibility, and steep changes in adjacent periods occur simultaneously, thus triggering stronger weight conservatism. The master controller then derives the reorganization weights accordingly. ; in, Let Kronecker function be used when The value is 1 if the suppression factor is small, and 0 otherwise. This option increases the self-holding ratio when the suppression factor is small, making the synthesis direction closer to the direction of the target linked object, thereby resisting the short-term reversal of the adjacent traction direction in adjacent cycles. Nonnegation and normalization are performed to eliminate numerical anomalies: ; When the denominator is zero, the main controller will And the rest This is to establish deterministic rules for handling degradation.

[0044] After obtaining the normalized renormalization weights, the master controller robustly performs hue vector synthesis. The master controller first constructs candidate synthesis vectors: ; The amplitude is detected to characterize the degree of cancellation caused by parallel traction. The main controller defines the amplitude: ; in, This refers to Euclidean norm operations. If A smaller value indicates a significant conflict between adjacent traction directions, leading to vector cancellation. To prevent noise from dominating the direction in this case, the main controller constructs an amplitude gating coefficient: ; in, and The gate threshold parameter is derived from the mode parameter table or user-configured input, and satisfies the following conditions: The main controller then generates the gated composite vector based on this: ; in, This is a normalization function; when the input vector norm is zero, the main controller will... Defined as To avoid division by zero. The above gating ensures that when adjacent traction cancels out and the amplitude is insufficient to provide a stable direction, the synthesized vector automatically reverts to the direction of the target linked object itself, thereby preventing the short-term reversal caused by parallel traction from pulling the synthesized direction towards the middle of the hue cycle.

[0045] The main controller inversely calculates the composite hue from the composite vector and obtains: ; in, It is the arctangent function in the fourth quadrant. and They are respectively The amount; Used to normalize the results to the selected hue period range.

[0046] For saturation and brightness, the main controller does not directly use the fixed-weight scalar coupling, but instead uses the same renormalized weights as hue. Achieving consistent synthesis and introducing visibility-related boundary conservatism makes adjacency traction more conservative at high visibility and critical boundaries. The master controller calculates: ; ; And impose constraints on the scope of the results: ; in, This is the truncation function; when saturation and brightness are expressed in a non-normalized manner, the main controller replaces the boundary in the above formula with the corresponding full-scale boundary and maintains the consistency of the truncation logic.

[0047] Furthermore, the master controller performs time continuity processing on the synthesized results, but the time continuity filter coefficients are not fixed constants, but are derived from the aforementioned decision variables, thereby enhancing time continuity under conditions of critical boundaries, high visibility, and steep changes. The master controller defines the time continuity coefficients: ; in, and The upper and lower limits of the continuity coefficients are derived from the model parameter table or user configuration input, and satisfy the following conditions: The main controller maintains the smoothed hue vector from the previous cycle. Previous period smoothed saturation previous cycle smoothed brightness And recursively apply the following formula: ; ; ; in, This is the smoothed hue vector. and These represent the smoothed saturation and brightness, respectively. The main controller... Perform normalization to avoid numerical drift: ; And inversely calculate the smooth hue from the smooth hue vector: ; in, and for The amount.

[0048] To prevent chain errors such as short-term reversal and locking during the synthesis process under short-term disturbances, the main controller introduces a holding constraint for situations where the traction direction alternates in dominance. The main controller also controls the target linkage object. Save the composite vector from the previous period And calculate the current candidate synthesis vector. Consistent with the direction of the synthesized vector from the previous period: ; The main controller sets a consistency threshold in the firmware. Its source is the mode parameter table or user configuration input; when And at the same time When at a high level, the main controller will adjust the gating coefficient for this cycle. Decrease according to a fixed rule, so that the composite vector of this period is directed towards or Rollback, rollback ratio from The calculation formula is naturally determined, thereby limiting the impact of the direction reversal of adjacent cycles on the synthesis result; the threshold and the backoff rule are both fixed by firmware or determined by user configuration input, so that the implementation has a reproducible operation definition.

[0049] Thus, within each control cycle, the main controller completes the intra-cycle reshaping and gating of the coupling weights by constructing the hue vector, visibility coefficient, boundary critical coefficient, adjacency traction consistency coefficient, and cycle change steepness coefficient, thereby obtaining a linked synthetic hue that maintains continuity near the hue cycle boundary. Linked synthesis saturation Combined brightness with linkage .

[0050] Furthermore, the smooth linkage color parameters of each linked object are obtained. Then, the main controller converts it into an object-level target color vector with red, green, and blue color components, and expands this object-level target color vector to the pixel unit level. To ensure that the conversion has a clearly defined formula, the main controller uses a standard piecewise conversion formula from hue, saturation, and lightness to red, green, and blue. The main controller first calculates: ; ; ; ; Where c represents chromaticity. For the normalized hue segment index, X is the intermediate hue measure, m is the matching item; p is the hue segment width constant, whose value depends on the definition of the hue unit: when the hue unit is angle and the range is [0, 360), p is 60; when the hue unit is normalized period and the range is [0, 1), p is 1 or 6. The main controller fixes the hue unit and the corresponding p value in the firmware to avoid inconsistencies caused by mixed units. Then the main controller... The selected interval is the component without a matching term. And take values ​​according to the segmentation rules: when hour, =(C,X,0); when hour, =(X,C,0); When 2 <3 o'clock, =(0,C,X); When 3 <4 o'clock, =(0,X,C); When 4 <5 o'clock, =(X,0,C); When 5 <6 o'clock, =(C,0,X).

[0051] The main controller ultimately obtains the object-level red, green, and blue components: ; ; ; in, , , For linkage objects The target color component value at the object level in the kth control cycle.

[0052] When the linked object includes white light channel control, the main controller further calculates the target component of the white light channel in step two. The purpose of the white light channel target component is to improve luminous efficiency or enhance the stability of low-saturation areas while maintaining color perception. The main controller defines the white light component using a minimum component extraction method. ; And white light stripping was performed on the red, green and blue components to obtain: ; ; ; in, , , This is to remove the red, green, and blue components from the white light at the object level. If the white light channel is not enabled in the implementation, the main controller will... Define as zero and keep = , = , = Whether white light stripping is enabled is given by the mode parameter table or user configuration input and stored as an enable flag in the runtime context.

[0053] The main controller expands the object-level target color components into pixel-level target color components. The expansion process uses the mapping function defined in step one. For any linked object The main controller traverses For each logical address 'a' in the main controller, the corresponding pixel unit 'p(a)' is determined. 'p(a)' is given by the pixel unit table field of the main controller, which maps logical addresses to pixel unit indices. This field originates from the address determination process in step one. The main controller generates pixel unit-level input components for each pixel unit 'p(a)': ; ; ; Further generation occurs when a white light channel is present: ; in, This represents the pixel-level input component value of pixel unit p(a) on channel c. To enable fine-grained linkage differences among pixel units within the same linkage object, the master controller allows the introduction of intra-pixel offsets or intra-pixel weights during expansion. These offsets or weights originate from extended fields of the pixel unit table in step one or user-configured inputs. For example, the master controller can define an intra-pixel phase offset for each pixel unit. and will Replace with Then perform the HSV to RGB conversion; The source is the pixel unit link sequence number, geometric position table, or user configuration table. The main controller stores the offset in the pixel unit table and reads it for use during calculation.

[0054] Finally, the main controller outputs a set of pixel-level input components: ; in, This represents the set of pixel units, which is derived from the number of pixel units and the set of pixel unit indices obtained from the enumeration in step one. Each element is obtained from the object-level color calculation, linkage coupling calculation, time smoothing calculation, and mapping expansion calculation in this step, and is stored in the frame buffer of the main controller in a structure of pixel unit index - channel component.

[0055] In step three, the main controller will use the pixel-level input component set obtained in step two. The data is converted into serial control data that can be parsed and latched by the built-in IC of each multi-color LED pixel unit, and then transmitted to the pixel unit link in the form of timing signals according to the physical transmission protocol of the pixel unit link. This conversion process includes: pixel unit-level channel calibration calculation, brightness and current constraint calculation, quantization and jitter calculation, driver frame structure encapsulation, and line encoding and transmission according to the transmission protocol.

[0056] First, the data structure of the driving frame is determined. A driving frame refers to a sequence of serial data sent by the main controller to the pixel unit links within a control cycle. This serial data sequence is obtained by sequentially concatenating multiple pixel unit data segments according to the cascaded order of the pixel unit links. A pixel unit data segment refers to a set of channel driving codes corresponding to a multi-color LED pixel unit. This set of channel driving codes includes at least red, green, and blue channel driving codes, and further includes a white light channel driving code if a white light channel exists. The main controller stores the mapping relationship between the pixel unit link cascaded order and logical addresses in the pixel unit operation table, and determines the arrangement order of the pixel unit data segments in the driving frame accordingly. This mapping relationship originates from the address determination or pixel unit enumeration result in step one.

[0057] The master controller then performs channel calibration calculations for each pixel unit to convert the pixel unit-level input components into calibrated channel control components. For any pixel unit... The main controller reads the channel gain vector of the pixel unit from the pixel unit operation table. Each gain coefficient originates from one of the factory calibration table, online calibration, or preset configuration in step one, and its storage location is determined in step one to be either the built-in IC register or the pixel unit operation table of the main controller. The main controller will output the pixel unit-level input components from step two. Multiplying this by the channel gain coefficient yields the channel-calibrated control component: ; Where 'c' is the channel identifier. This refers to the control component after channel calibration. The multiplicative calibration aims to compensate for differences in channel luminous efficiency between pixel units, and it is used to perform a proportional adjustment on the input component before subsequent nonlinear mapping and quantization. Next, the main controller applies amplitude constraints to the channel-calibrated control components to ensure that the component values ​​fall within the allowable range and to avoid overflow. The main controller defines the full-scale range of the input components in the firmware. The The choice of color component representation method determines the color component representation: when the color component is represented by normalized real numbers, Defined as 1; when color components are represented by integers, Defined as the maximum representable value for this integer bit width. The main controller applies a saturation constraint to each channel: ; in, This is a truncation function used to restrict the input to a range. Inside, This represents the truncated control component. The truncation function is implemented using comparison and conditional assignment operations, and its parameters are given by the variables defined in this step.

[0058] After completing the amplitude constraints, the main controller performs nonlinear mapping calculations on each pixel unit to map the control components to drive code values. The main controller reads the gamma parameters of the pixel unit from the pixel unit operation table. Or lookup table ,in or The source, acquisition method, and storage location are all determined in step one. The main controller defines the full-scale range of the driver code in the driver code field. The The bit width of the channel driver code is determined by the built-in IC. This bit width is defined by the built-in IC specifications or the communication protocol and configured by the main controller in the firmware. If the gamma parameter method is used, the main controller calculates the unquantized driver code using the following formula: ; in, For unquantized driver code, the exponentiation is implemented by the main controller using floating-point arithmetic, fixed-point approximation, or a lookup table, and the selected implementation method is fixed in the firmware. If the lookup table method is used, the main controller calculates the unquantized driver code using the following formula: ; The construction method of the lookup table input index is as follows: The representation method is determined when Direct indexing when the value is an integer, when... When dealing with normalized real numbers, they are first mapped to discrete indices according to a proportional ratio before being indexed; this proportional mapping rule is fixed in the firmware by the main controller.

[0059] After nonlinear mapping, the main controller performs current constraint calculations to ensure that the channel output current meets the current calibration and upper limit constraints of the pixel unit. The main controller reads the current calibration coefficients from the pixel unit operation table. The The current is derived from the current sampling calibration, online calibration, or preset typical coefficients in step one. The main controller uses the current target relationship given in step one: ; in, The reference constant current value is derived from the constant current level specified in the built-in IC specifications or a reference value given in the configuration file. To enable constrained operation, the main controller defines the maximum allowable constant current per channel in its firmware. The The source of this value is the built-in IC specification allowable value or the product safety design allowable value, which the main controller hardens into the configuration parameter. The main controller then... The driving code scaling factor is obtained from the constraints, and scaling is performed on the channel driving code. To avoid introducing undefined solution processes, the main controller adopts an explicit scaling method: first, the channel current ratio is calculated: ; in, To limit the drive code to the scaling factor corresponding to the maximum allowable current; when When it means no scaling is needed, The time indicates that scaling is required. Based on this, the main controller obtains the unquantized drive code after current constraint: ; in, Used to select whether to scale. Used to further restrict to the range of driver code.

[0060] The main controller performs quantization operations on the current-constrained unquantized drive code to generate integer drive code that can be encapsulated into pixel unit data segments. The input for quantization is... Quantization output bit width and Consistent. The main controller determines whether the quantization rule originates from a firmware-fixed rule or a user-configured selection, and supports at least one of rounding quantization and jitter quantization. If rounding quantization is used, the main controller obtains the integer drive code using the following formula: ; in, This is a rounding function, implemented by adding 0.5 and rounding down, or by equivalent fixed-point arithmetic. If jitter quantization is used, the main controller introduces a quantization jitter term. The quantization jitter term is used to average the fractional part over multiple control cycles to a target value to reduce banding artifacts. The quantization jitter term originates from the output of a pseudo-random number generator or an error diffusion accumulator, and the main controller fixes its generation method in the firmware and records its random seed or initial accumulation value to meet reproducibility requirements. The jitter quantization is calculated as follows: ; in, This is the floor function; The range of values ​​is determined by the main controller according to the quantization error control requirements. For example, it can be a uniformly distributed random number in [0,1) or a decimal compensation amount calculated from the error diffusion state. Regardless of the method used, the main controller fixes its generation rule as a firmware algorithm. After obtaining the integer driving code for each channel of each pixel unit Subsequently, the main controller constructs the pixel unit data segment and encapsulates the drive frame. The field order of the pixel unit data segment is determined by the built-in IC's requirements for channel arrangement, which originate from the built-in IC specifications or communication protocol definition. The main controller fixes the field order in the firmware using a channel order configuration item, for example, it can be configured as red, green, blue or green, red, blue, and this configuration item remains consistent throughout the entire scheme. The main controller constructs the pixel unit data segment for pixel unit p: ; in, For pixel unit data segments, This refers to the channel identifier sequence determined by the channel order configuration item. The main controller concatenates all pixel unit data segments in the pixel unit link concatenation order to obtain the drive frame payload: ; in, For concatenation operations, This is a sequence of pixel unit indices arranged in a cascaded order, derived from the enumeration result or configuration table of step one.

[0061] To improve transmission reliability and enable the receiver to detect transmission errors, the master controller can attach a check field to the drive frame payload. The purpose of the check field is to perform integrity checks on the drive frame payload, and its generation method is fixed by the master controller as either Cyclic Redundancy Check (CRC) or a simple checksum. CRC is defined as obtaining a check value by performing modulo-2 division on a preset generator polynomial of the drive frame payload bitstream; this generator polynomial is given by the protocol specification or firmware configuration. To ensure that this check has a clear computational expression, the master controller represents CRC as: ; in, This indicates the function used to calculate the Cyclic Redundancy Check (CRC) using a generator polynomial (poly), the poly of which is derived from the protocol specification or configuration file. The master controller appends the CRC as either a frame tail field or a frame header field to the drive frame, the specific appending location being determined by the protocol specification or configuration item.

[0062] After encapsulating the driver frame structure, the main controller performs line encoding on the driver frame according to the physical transmission protocol of the pixel unit link and then sends it. Line encoding refers to the process of mapping the bit sequence of the driver frame to physical levels and timing pulses. The mapping rules are derived from the physical layer protocol definition used, and the main controller selects this fixedly in the firmware via a protocol type configuration item. To ensure full transparency, the main controller provides implementation paths for at least two types of line encoding methods; the specific method used is determined and fixed by the product selection: When using a single-line pulse width encoding protocol, the master controller maps logic 1s and logic 0s in the drive frame bit sequence to pulse waveforms with different high-level durations, and outputs them continuously with a fixed bit period. The master controller stores logic 1 pulse parameters and logic 0 pulse parameters in its firmware; these pulse parameters are derived from the built-in IC timing specifications or timing parameters verified by an oscilloscope. The master controller generates these pulse waveforms through hardware timers, direct memory access, or dedicated peripherals and outputs them to the data lines of the pixel unit link. After completing the entire frame output, the master controller maintains a low-level time no less than the built-in IC latch time to allow each pixel unit to latch its received pixel unit data segment; this latch time is derived from the built-in IC specifications or verified latch conditions.

[0063] When using a two-wire clock or data protocol, the master controller will synchronously output the drive frame bit sequence to the data line at the clock edge, and output it according to the clock polarity, phase, and bit order specified in the protocol. The master controller stores the clock frequency, sampling edge, and bit order configuration in its firmware, which is derived from the built-in IC communication specification or user configuration input. The master controller outputs clock and data through serial peripherals and outputs a frame start marker or chip select control signal at the frame boundary to meet the frame synchronization requirements of the built-in IC.

[0064] During transmission, the master controller updates the driver frames according to the control cycle, and takes the completion of the transmission of the driver frame in the current cycle as the end condition for the transmission action in that cycle. The master controller determines the completion criterion for the transmission action as: all bits of the driver frame have been output and the latching condition is met; when a protocol with a check field is used, the master controller will also output the check field and meet the corresponding frame end condition. The master controller records the protocol type, channel order configuration item, driver code bit width configuration item, and check method configuration item used for transmission in the runtime context, so that the structure of the driver frames generated for each transmission under the same configuration remains consistent.

[0065] In step four, the meaning and triggering method of synchronous update are first defined. Synchronous update refers to the process whereby the main controller, after sending the corresponding drive frame for the current control cycle at the control cycle boundary and satisfying the built-in IC latching condition, causes the multi-color LED pixel units on the pixel unit link to enter the state of displaying according to the new drive frame within the same control cycle. The main controller defines the control cycle sequence number as kkk and the control cycle boundary time as: ; in, At the starting time, For the control cycle, both the time base definition and timer configuration of the main controller described in step two are used. The main controller executes a drive frame transmission action once within each control cycle, and the completion of the drive frame transmission and the fulfillment of the latching condition are used as the conditions for synchronous updates in that cycle. The latching condition is specified by the pixel unit link physical transmission protocol: when using a single-wire pulse width encoding protocol, the latching condition is that the data line remains low for a period not less than the built-in IC latching time; when using a dual-wire clock or data protocol, the latching condition is that the frame end marker output is complete or the chip select control signal returns to the non-selected state and the setup and hold time specified by the built-in IC is met. The latching time or setup and hold time is derived from the built-in IC specifications or timing parameters verified by an oscilloscope. The main controller stores this time as a protocol parameter in the operating context and executes the corresponding delay or control signal hold action after each transmission to satisfy the latching condition.

[0066] After the synchronization update is established, the main controller performs feedback acquisition to obtain observation data for calibration closed-loop calculation. Feedback quantity refers to a measurement quantity that can characterize the output state of the pixel unit link. The main controller adopts at least one of the following feedback quantity sources and fixes the adopted source in the form of configuration items to make the method of obtaining feedback quantity explicit and reproducible.

[0067] When the product has a current sampling circuit, the main controller collects the current feedback value. The current sampling circuit refers to a combination of a sampling resistor and an analog-to-digital converter connected in series in the pixel unit link power supply circuit or segmented power supply circuit; its output is a digital value proportional to the supply current. After the latching condition is met, the main controller reads the analog-to-digital converter output within a preset sampling window to obtain the current feedback value. ,in This represents the sampled current value in the k-th control cycle. The sampling window is sourced from firmware configuration or user configuration input, and the main controller limits the sampling window in the firmware to a stable time period after latching is completed to avoid acquiring transient currents during transmission. The main controller converts the sampled current into a normalized current feedback quantity. ; in, This is the normalized current feedback quantity; The baseline current in the zero-output state is derived from the measurement when all pixel units are off; This is the reference current under the reference output state, sourced from the measured value under the preset reference drive frame. It is measured by the main controller during production calibration or field calibration. and And store it as calibration parameters; when calibration is not performed, the main controller will and The values ​​are given by preset typical values, which are derived from the statistical results of sampling measurements and are stored in the configuration file.

[0068] When the product is equipped with an optical sensor, the main controller acquires the optical feedback quantity. An optical sensor is a sensor capable of measuring light intensity or color, and its output is a digital quantity related to brightness or red-green-blue components. After the latching condition is met, the main controller reads the optical sensor output within a preset sampling window to obtain the optical feedback quantity. If the optical sensor output is a brightness measurement value, then the brightness feedback quantity is defined as... If the optical sensor outputs red, green, and blue measurements, then the color feedback quantity is defined as... The main controller normalizes the optical feedback values, and the brightness is normalized as follows: ; in, This is the normalized brightness feedback value; The baseline brightness is extinguished, and the source is a full-extinguish measurement; The reference brightness is derived from a reference drive frame measurement. For color feedback, the main controller normalizes it as follows: ; in, This is the normalized color feedback amount; The reference color measurement value is derived from the measurement result under the reference driving frame. The main controller defines the reference driving frame as a fixed calibration frame, which is sent by the main controller during production calibration or field calibration. Its content is given by the firmware configuration, such as the ability to select a combination sequence of lighting only the red channel, only the green channel, only the blue channel, or all channels, and obtain the corresponding reference measurement value through the sensor.

[0069] When the product lacks a current sampling circuit and an optical sensor, the main controller performs model-based self-calibration. Model-based self-calibration means that the main controller does not use external measurements, but instead uses a built-in IC-based current and temperature model to calculate output changes and correct parameters accordingly. To ensure this method is fully disclosed, the main controller defines the ambient temperature... The source of the temperature change is either a temperature sensor or a built-in IC temperature register; if neither exists, the main controller will fix the temperature change term to zero and only perform parameter limiting, without recursive updates. The main controller defines the current temperature coefficient. The temperature drift coefficient is given by the built-in IC specification or obtained by calibration fitting, and a prediction ratio is established based on this: ; in, For the temperature drift prediction ratio, This is a reference temperature, sourced from the calibration temperature or a preset reference temperature.

[0070] After obtaining the feedback and completing normalization, the master controller constructs a target value and calculates the error accordingly. The target value refers to the expected output index obtained by the master controller based on the driving frame and the calculation model in the current control cycle. The master controller constructs at least one of the brightness target value and the color ratio target value, and limits the source of the target value to the driving code sent in this cycle and the reference parameters stored in the pixel unit operation table.

[0071] When constructing the target brightness value, the main controller represents the desired brightness as a weighted sum of the driving codes in the current cycle, and defines: ; in, This is the normalized target brightness value; It is the integer driving code of the p channel c of the pixel unit in the k-th period, which comes from the quantization output in step three; The driver code is at full scale, and its source is the built-in IC bit width configuration; These are channel weighting coefficients, used to represent the relative weight of different channels' contribution to brightness. They are derived from luminous efficacy calibration data or preset typical weights. The main controller will... Store as configuration parameters and use typical values ​​from the same batch under uncalibrated conditions; if calibration conditions are used, then It is calculated from the proportion of brightness contribution measured when a single channel is lit.

[0072] When constructing the target color ratio, the main controller represents the desired color ratio using the channel ratio of the current cycle's drive code, and defines: in, This is the color ratio target vector. The source of this target vector is the summation calculation of the drive code for this cycle, therefore it remains consistent with the actual transmitted data. To avoid division by zero, the main controller will... It is defined as the target vector of the previous cycle or as a preset reference vector, and this definition is fixed by the firmware.

[0073] After constructing the target quantity, the main controller calculates the error quantity based on the selected feedback type. If current feedback or brightness feedback is used, the main controller calculates the brightness error: ; in, This is the normalized brightness feedback value; when using current feedback value, it is... Alternative And keep the formula form unchanged. If color feedback is used, the main controller calculates the color ratio error vector: ; in, To normalize the color feedback amount, Let be the target vector for color proportion. If the temperature drift prediction proportion is used as the model feedback, then the main controller defines the brightness error as: ; in, It originates from the temperature drift prediction ratio formula, and this definition represents the drift error relative to the reference temperature conditions.

[0074] After obtaining the error value, the main controller performs a recursive update of the calibration parameters in the pixel unit operation table. The recursive update uses an update step size parameter to control the update magnitude; this update step size parameter is denoted as... The update parameters are sourced from mode parameter tables, user configuration inputs, or firmware presets, and are limited to positive numbers in the firmware to ensure controllable update direction. The main controller employs different update strategies for different types of calibration parameters, and clearly defines the inputs, outputs, and constraints of each strategy.

[0075] For current calibration coefficient The main controller uses a proportional recursive update method. The main controller will adjust the brightness error... As a global error, and performed on each pixel unit: ; in, This refers to the current calibration coefficient used in the k-th cycle. The updated current calibration coefficient; The current calibration update step size is derived from the configuration parameters; and The allowable range of the current calibration coefficient is derived from the boundary between the allowable current range of the built-in IC and the safe current range of the product, or from the boundary given by calibration experience, and is fixed in the form of configuration parameters. This is used to limit update results to within the allowed range, thereby preventing updates from causing overcurrent or abnormal brightness.

[0076] For channel gain vector The main controller has color feedback quantity Channel gain updates are performed periodically; if no color feedback is available, the channel gain is not updated or only limiting is performed. If color feedback is available, the main controller will update the color scaling error vector. To update the channel gain, the following recursive method is used: ; in, Let c be the gain coefficient of the p-channel of the k-th period pixel unit. This is the updated gain coefficient; The channel gain update step size is derived from configuration parameters; and The channel gain is the allowable range, derived from a calibrated reasonable range or product experience range, and is fixed as a configuration parameter. This update formula is driven by the color ratio error component, causing the corresponding channel gain to adjust according to the error direction, and limiting the amplitude to ensure that the gain does not undergo uncontrollable amplification or reduction.

[0077] gamma parameters Or lookup table The main controller employs a low-frequency update strategy, meaning it only updates when stable conditions are met, to avoid introducing visible flickering during rapid dynamic color transitions. For example... Figure 3 As shown, the main controller defines stability conditions as follows: the absolute value of the brightness error is lower than the error threshold within a certain number of consecutive control cycles, or the driving frame is a preset calibration frame. The error threshold and the number of consecutive cycles are given by configuration parameters, which are derived from production calibration experience or user configuration input. If gamma parameters are used... And meet the stability conditions, the main controller... Perform a recursive update: ; in, The step size for updating gamma parameters is derived from configuration parameters; and The allowable range for gamma parameters is derived from empirical or calibration ranges and is permanently set as configuration parameters. If a lookup table is used... When the stability conditions are met, the main controller performs proportional or segmented adjustments to the lookup table; taking proportional adjustment as an example, the main controller scales the lookup table output: ; Where x is the input index of the lookup table. For the updated lookup table, The lookup table update step size is derived from configuration parameters. The main controller writes the updated lookup table to non-volatile memory or to the built-in IC curve register, and performs verification before and after writing to ensure successful writing; the verification can be read-back comparison or cyclic redundancy check comparison, and the verification method is fixed and recorded by the firmware.

[0078] After completing the recursive update, the main controller performs parameter writing or parameter storage to make the updated calibration parameters effective in subsequent control cycles. If the built-in IC supports online writing to the calibration register, the main controller sends a parameter writing frame before or after sending the drive frame, storing the updated parameters. , , or Write to the corresponding register; the field structure and address field usage of the write frame are consistent with step one, and the main controller performs readback verification or status code verification after writing to confirm successful writing. If the built-in IC does not support online writing to the calibration register, the main controller stores the updated parameters in the pixel unit operation table and reads and uses them in step three of the next control cycle to make the update effective. The main controller uses a fixed structure or fixed table entry format for the parameter storage write location and data format, and defines the meaning and unit of each field in the firmware to avoid the use of undefined parameters.

[0079] In step four, the main controller also performs closed-loop update safety constraints to prevent uncontrolled parameter updates under abnormal feedback conditions. The main controller defines abnormal feedback conditions as: feedback quantity exceeding the physically interpretable range, feedback quantity abruptly exceeding the abrupt threshold, or feedback acquisition failure. The physically interpretable range is determined by the sensor range, analog-to-digital converter range, or the allowable current range of the built-in IC; the abrupt threshold is given by configuration parameters and derived from empirical settings or calibration statistics. When the main controller detects an abnormal feedback condition, it either stops the parameter recursive update for the current cycle and keeps the parameters unchanged from the previous cycle, or it rolls back the parameters to a safe range according to the limiting boundary; the stopping or rollback strategy is determined by firmware configuration items, and an abnormal flag is recorded in the runtime context for diagnostic purposes.

[0080] This invention also proposes a multi-color LED built-in IC color linkage control system, including: an initialization pixel unit consistency configuration module, a color linkage calculation module, a drive frame generation encoding and sending module, a synchronous update calibration closed-loop module, and signal connections between the modules; The initialization pixel unit consistency configuration module is used by the main controller to send a reset sequence to the pixel unit link after the power supply is stable, determine the logical address and number of pixel unit links, divide the pixel unit into multiple linkage objects according to the physical continuous interval, geometric position or user-configured grouping information recorded in the preset grouping table, generate a mapping from each linkage object to the pixel unit address subset, and establish a coupling weight matrix between linkage objects according to the adjacency relationship, distance attenuation or same group priority rules. The color calculation module of the holographic linkage is used by the main controller to sample the hue function, saturation function, and brightness function in each control cycle. The hue is rewritten as a two-dimensional vector composed of cosine and sine, and the brightness visibility coefficient, boundary critical coefficient, traction consistency index, and cycle change steepness coefficient are constructed. Based on this, the coupling weight matrix is ​​reorganized and limited row by row in cycle to obtain the reorganized weight. The hue vectors of the target linkage object and its adjacent linkage objects are weighted and summed according to the reorganized weight to obtain the candidate synthesis vector. Then, the gate coefficient is mixed and normalized, and the time continuous coefficient is recursively fused to obtain smooth hue, saturation, and brightness. After being converted into red, green and blue components, they are expanded into a set of pixel unit-level input components by mapping the pixel unit address subset. The drive frame generation, encoding, and sending module is used by the main controller to encapsulate the set of pixel unit-level input components into a drive frame spliced ​​from pixel unit data segments and send it to the pixel unit link; The synchronous update calibration closed-loop module is used by the main controller to trigger synchronous update after the drive frame is sent and the built-in chip latch timing is met. It collects feedback quantities and normalizes them, constructs brightness target quantities or color ratio target quantities, calculates brightness errors or color ratio errors, and recursively updates calibration parameters according to the update step size and limits the amplitude.

[0081] The above formulas are all dimensionless calculations. The formulas are derived from software simulations based on a large amount of collected data to obtain the most recent real-world results. The preset parameters in the formulas are set by those skilled in the art according to the actual situation.

[0082] The above embodiments can be implemented, in whole or in part, by software, hardware, firmware, or any other combination thereof. When implemented using software, the above embodiments can be implemented, in whole or in part, in the form of a computer program product.

[0083] Those skilled in the art will recognize that the modules and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and inventive constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0084] In addition, the functional modules in the various embodiments of this application can be integrated into one processing module, or each module can exist physically separately, or two or more modules can be integrated into one module.

[0085] The above description is merely a specific embodiment 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. Therefore, the scope of protection of this application should be determined by the scope of the claims.

[0086] In conclusion, the above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the protection scope of the present invention.

Claims

1. A multi-color LED built-in IC color linkage control method, characterized in that, include: After the power supply is stable, the main controller sends a reset sequence to the pixel unit link, determines the logical address and number of the pixel unit link, and divides the pixel unit into multiple linkage objects according to the physical continuous interval, geometric position or user-configured grouping information recorded in the preset grouping table. It generates a mapping from each linkage object to a subset of pixel unit addresses and establishes a coupling weight matrix between linkage objects according to adjacency, distance attenuation or group priority rules. In each control cycle, the main controller samples the hue function, saturation function, and brightness function, rewrites the hue as a two-dimensional vector composed of cosine and sine, and constructs the brightness visibility coefficient, boundary critical coefficient, traction consistency index, and cycle change steepness coefficient. Based on this, the coupling weight matrix is ​​reorganized and limited row by row in cycle to obtain the reorganized weight. The hue vectors of the target linkage object itself and its adjacent linkage objects are weighted and summed according to the reorganized weight to obtain the candidate synthesis vector. Then, the gate coefficient is mixed and normalized, and the time continuous coefficient is recursively fused to obtain smooth hue, saturation, and brightness. After being converted into red, green, and blue components, they are expanded into a set of pixel unit-level input components by mapping the pixel unit address subset. The main controller encapsulates the set of pixel-level input components into a driving frame spliced ​​from pixel-level data segments and sends it to the pixel-level link; After the drive frame is sent and the built-in chip latch timing is met, the main controller triggers a synchronous update, collects and normalizes the feedback quantity, constructs the target brightness quantity or the target color ratio quantity, calculates the brightness error or the color ratio error, and recursively updates the calibration parameters according to the update step size and limits the amplitude.

2. The multi-color LED built-in IC color linkage control method according to claim 1, characterized in that: After the power supply is stabilized, the main controller sends a reset sequence to the pixel unit link to clear the residual state. Then, it determines the logical address and quantity of each pixel unit by recursion of address writing or enumeration in cascade order, and establishes the correspondence between pixel unit index and physical location.

3. The multi-color LED built-in IC color linkage control method according to claim 2, characterized in that: After obtaining the logical address, the main controller loads and writes the color channel gain parameters, nonlinear mapping parameters, and constant current calibration parameters into the registers or to the main controller for calculation on a pixel-by-pixel basis, depending on whether the built-in chip supports the corresponding registers. Then, a preset grouping table is read. The grouping table records at least the correspondence between the logical address of each pixel unit and the identifier of the linked object, or records the physical continuous interval, geometric position area or user-configured grouping rules. The main controller merges the logical addresses of pixel units with the same linked object identifier or satisfying the same grouping rules into the same linked object according to the grouping table, thereby dividing the pixel unit into multiple linked objects and generating a corresponding pixel unit address subset mapping for each linked object. Simultaneously, a coupling weight matrix is ​​generated between linked objects based on their topological adjacency, geometric distance attenuation, or group priority rules.

4. The multi-color LED built-in IC color linkage control method according to claim 3, characterized in that... The main controller calculates the target color vector and target brightness scalar for each linked object in each control cycle, and expands the linked object-level results into pixel-level color components according to the mapping from object to pixel unit. The main controller adopts a unified parameterization method for hue, saturation, and brightness, establishing hue, saturation, and brightness functions for each linked object, and using the mapping between the control cycle number and the control cycle to the equivalent time as independent variables. The main controller generates the basic hue by linearly advancing the modulo operation or by advancing the hue lookup table, and then determines the phase offset based on the linked object number, geometric position, or user configuration, and performs translation and modulo operation on the basic hue to obtain the offset hue. Simultaneously, it reads fixed values ​​of saturation and brightness from the mode parameter table or user configuration, or generates saturation and brightness that change over time according to a preset waveform function; After obtaining the trajectory parameters of each linked object, the main controller applies the coupling weight matrix to the parameters or their equivalent vector representation.

5. The multi-color LED built-in IC color linkage control method according to claim 4, characterized in that: After sampling the hue, saturation, and brightness functions of each linked object in each control cycle, the main controller rewrites the hue from a scalar into a two-dimensional vector composed of cosine and sine. It then obtains the brightness visibility coefficient by multiplying saturation and brightness, the boundary critical coefficient by the minimum distance from the hue to the cycle endpoint, the relative direction quantity by the dot product of the current hue vector and each adjacent hue vector, and calculates the traction consistency index in conjunction with the coupling weights. Finally, it obtains the cycle change steepness coefficient by the dot product of the current and previous cycle hue vectors. Based on the above multi-factor judgment quantities, the main controller reorganizes and limits the coupling weight matrix row by row on a cycle-by-cycle basis: it constructs a confidence factor for each adjacent object according to the relative direction quantity, and constructs a boundary-oriented suppression factor for the target object according to the boundary critical coefficient, brightness visibility coefficient, and change steepness coefficient. The suppression factor is then used to interpolate between the original coupling weight contribution and the self-holding ratio to generate reorganized weights. Finally, the reorganized weights are nonnegated and normalized, and a degenerate assignment is given when the denominator is zero.

6. The multi-color LED built-in IC color linkage control method according to claim 5, characterized in that: Under the rebalancing weights, the main controller multiplies the hue vector of the target linked object itself and the hue vectors of each adjacent linked object with which it is coupled by the corresponding rebalancing weights, and then performs a weighted summation to obtain a candidate composite vector. The magnitude of the candidate composite vector is calculated, and then a gating coefficient is constructed according to the magnitude. The candidate composite vector is mixed with the hue vector of the target object itself according to the gating coefficients and normalized to obtain a gated composite vector. Then, the linked composite hue is inversely calculated by the four-quadrant arctangent and modulo normalization. The main controller uses the same rebalancing weight as the hue to perform consistent weighted synthesis of saturation and brightness and performs range truncation. The main controller derives a time continuity coefficient from the boundary critical coefficient, brightness visibility coefficient and change steepness coefficient. According to this coefficient, the current period gated composite vector and saturation, brightness and smoothing amount of the previous period are recursively fused and the smoothed hue vector is normalized, and then the smoothed hue is inversely calculated.

7. The multi-color LED built-in IC color linkage control method according to claim 6, characterized in that: The main controller saves the gating synthesis vector of the previous cycle and calculates the directional consistency with the candidate synthesis vector of the current cycle. When the consistency is low and the boundary is critical and the visibility is at a high level, the gating coefficient is lowered according to a fixed rule to make the synthesis vector back towards the direction of the target object itself or the synthesis direction of the previous cycle. After obtaining the smooth hue, saturation and brightness of each linked object, the main controller completes the calculation of hue, saturation and brightness to red, green and blue components according to the standard piecewise formula. When the white light channel is enabled, the white light component is extracted according to the minimum components of the three colors, and white light stripping is performed on red, green and blue to obtain the stripped three color components. The main controller then expands the object-level color components to the pixel unit-level channel input components according to the mapping of the linked object to the pixel unit address subset. During the expansion, the phase offset within the pixel unit can be introduced to replace the smooth hue before performing color component conversion. Finally, the pixel unit index and each channel input component are written to the frame buffer.

8. The multi-color LED built-in IC color linkage control method according to claim 7, characterized in that... The main controller determines the structure of the driving frame, which consists of multiple pixel unit data segments concatenated sequentially, based on the pixel unit link cascading order, and determines the arrangement of each pixel unit data segment according to the mapping from logical address to cascading order. The main controller reads the channel gain parameter from the operation table for each pixel unit, multiplies the pixel unit-level input component with the channel gain and truncates the range, then reads the gamma parameter or looks up the table to perform nonlinear mapping on the truncated component to obtain the driving code domain value, and reads the current calibration coefficient and the reference constant current value to calculate the current constraint proportional coefficient, scales the driving code domain value proportionally and truncates the driving code range. The main controller performs jitter quantization on the scaled drive code field values ​​by rounding or introducing pseudo-random numbers or error diffusion to obtain integer drive codes. Then, according to the channel sequence configuration, the integer drive codes of each channel are encapsulated into pixel unit data segments and concatenated in a cascaded order to form the drive frame payload. Cyclic redundancy check or checksum fields are appended to the frame header or frame tail according to the configuration. The main controller maps the drive frame bit sequence into line timing signals according to the selected physical layer protocol and sends them. The single-line protocol uses pulse width ratio mapping and is output by timer, direct memory access or dedicated peripheral. The two-line protocol outputs data synchronously according to the clock edge and outputs the clock and data by serial peripheral. At the end of the frame, a low-level hold or frame synchronization control signal is output according to the latch time condition.

9. The multi-color LED built-in IC color linkage control method according to claim 8, characterized in that: The main controller uses the control cycle boundary as a reference. After the drive frame in this cycle ends and the built-in chip latch timing is met, it triggers a synchronous update and determines the latching condition according to the low-level hold time of the single-wire protocol or the frame end mark, chip select signal and setup hold time of the two-wire protocol. After latching, the main controller selects the feedback source according to the configuration and collects the current sampling quantity or optical brightness quantity, red, green and blue measurement quantity in the preset sampling window, or calculates the temperature drift prediction ratio based on the temperature and current model, and normalizes the feedback quantity based on the extinguishing baseline and the reference drive frame measurement value. The main controller constructs the target brightness or color ratio based on the drive code and reference parameters of the running table sent in the current cycle, and calculates the brightness error or color ratio error according to the feedback type. The main controller performs proportional recursion and amplitude limiting on the current calibration coefficient according to the update step size, recursively and amplitude limiting the channel gain according to the channel error component when color feedback is available, and performs low-frequency recursion or proportional adjustment and amplitude limiting on the gamma parameters or lookup table when the stability condition is met or the calibration frame is in progress. The main controller selects to send the updated parameters to the frame according to whether the built-in chip supports online writing and performs readback or verification comparison, or writes them to the running table for the next cycle to read. When the feedback quantity exceeds the limit, changes abruptly, or the acquisition fails, the main controller stops the recursion according to the configuration or backtracks according to the amplitude limiting boundary and records the abnormal flag.

10. A multi-color LED built-in IC color linkage control system, used to implement the multi-color LED built-in IC color linkage control method according to any one of claims 1-9, characterized in that, include: Initialize the pixel unit consistency configuration module, the color calculation module for the color linkage, the driver frame generation, encoding and sending module, the synchronous update calibration closed-loop module, and the signal connection between each module; The initialization pixel unit consistency configuration module is used by the main controller to send a reset sequence to the pixel unit link after the power supply is stable, determine the logical address and number of pixel unit links, divide the pixel unit into multiple linkage objects according to the physical continuous interval, geometric position or user-configured grouping information recorded in the preset grouping table, generate a mapping from each linkage object to the pixel unit address subset, and establish a coupling weight matrix between linkage objects according to the adjacency relationship, distance attenuation or same group priority rules. The color calculation module of the holographic linkage is used by the main controller to sample the hue function, saturation function, and brightness function in each control cycle. The hue is rewritten as a two-dimensional vector composed of cosine and sine, and the brightness visibility coefficient, boundary critical coefficient, traction consistency index, and cycle change steepness coefficient are constructed. Based on this, the coupling weight matrix is ​​reorganized and limited row by row in cycle to obtain the reorganized weight. The hue vectors of the target linkage object and its adjacent linkage objects are weighted and summed according to the reorganized weight to obtain the candidate synthesis vector. Then, the gate coefficient is mixed and normalized, and the time continuous coefficient is recursively fused to obtain smooth hue, saturation, and brightness. After being converted into red, green and blue components, they are expanded into a set of pixel unit-level input components by mapping the pixel unit address subset. The drive frame generation, encoding, and sending module is used by the main controller to encapsulate the set of pixel unit-level input components into a drive frame spliced ​​from pixel unit data segments and send it to the pixel unit link; The synchronous update calibration closed-loop module is used by the main controller to trigger synchronous update after the drive frame is sent and the built-in chip latch timing is met. It collects feedback quantities and normalizes them, constructs brightness target quantities or color ratio target quantities, calculates brightness errors or color ratio errors, and recursively updates calibration parameters according to the update step size and limits the amplitude.

Images