How to Specify a UCS2904 RGBW LED Profile Light for Architectural and Floor Projects
An addressable profile can look continuous in a rendering yet reveal visible steps on site, or produce the right animation while sending light toward the wrong surface. The useful question is not whether an RGBW profile can change colour, but whether its pixel rhythm, optical direction, housing and control architecture match the viewing distance and installation detail.
Published configuration at a glance
Define the visual job before choosing pixel density
Floor guidance, architectural outlines and decorative colour movement are different tasks. A floor line may prioritise a readable path and controlled glare; a facade detail may prioritise rhythm from a distance; a commercial feature may need chases and colour transitions. Define the primary viewing position, movement speed and whether the line should read as separate pixels or as a smoother luminous band.
For close-view graphics or text, 10 pixels/m may show steps that a distant architectural outline would hide. Higher LED count alone does not change the number of controllable pixels in this model.
What 10 pixels/m means at the viewing distance
The page lists 10 pixels/m, so the calculated centre-to-centre control pitch is 1000 mm ÷ 10 = 100 mm. This is a control-pixel interval, not a claimed cutting interval. The page also lists 60 LEDs/m, meaning the optical source density is higher than the control density.
At medium or long viewing distances, a 100 mm control rhythm can support segment chases, gradients and directional movement. Projects needing close-view lettering, fine media effects or smaller visible steps should compare a denser pixel configuration before sampling.
RGBW and UCS2904: plan cascade data correctly
The published configuration identifies RGBW, UCS2904 and DC24V. RGBW provides a dedicated white channel in addition to red, green and blue; the white colour temperature and channel behaviour are not published and should be frozen with the sample.
UCS2904 is treated here as a cascade-pixel architecture. Plan pixel count, data direction, colour order, controller compatibility, port allocation and mapping. Do not describe each pixel as an independently set DMX address unless the selected upper-level controller explicitly maps the data to DMX or Art-Net.
A 21×26 mm profile is part of the installation detail
The aluminium housing is listed as 21×26 mm. That physical envelope affects recess dimensions, channel alignment, cable exits, corner treatment and access for replacement. A drawing that shows only the luminous line is not enough to approve the installation detail.
The product page mentions floor projects, but it does not publish walk-over load, impact rating, slip classification or IP rating. A recessed floor application therefore needs a separate review of cover, drainage, sealing, structural support and maintenance access.
Use the 120° output as an optical starting point
The page lists a 120° lighting angle. Treat it as the starting optical distribution, not proof of uniform light on every surface. Distance to the illuminated surface, diffuser, recess depth, profile orientation and nearby edges determine whether the result appears broad, hidden or uneven.
Before quantity production, install a short mock-up in the intended orientation and judge it from the real viewing positions. A correct sample answers both questions: is the pixel step acceptable, and is the light directed where the design expects?
Quick project decision table
| Project condition | Decision | Why |
|---|---|---|
| Medium-distance outline or guidance | Evaluate the 100 mm pixel rhythm with a mock-up | 10 pixels/m is published for this model |
| Close-view text or fine media effect | Compare a denser pixel option | Smaller visible steps need more control points |
| Smooth linear appearance | Judge diffuser, orientation and viewing distance | 60 LEDs/m does not guarantee invisible pixel steps |
| Recessed floor detail | Check the 21×26 mm envelope and service access | Walk-over and IP data are not published |
| RGB plus usable white scenes | Confirm the RGBW sample and white specification | White-channel CCT is not listed |
| Programmable zones and motion | Plan cascade direction, ports and mapping | UCS2904 is not automatically DMX addressing |
LIKELIGHT product case: where this configuration fits
The LIKELIGHT configuration combines DC24V, UCS2904 RGBW cascade control, 60 LEDs/m, 10 pixels/m, a 21×26 mm aluminium profile and 120° output. It is a practical candidate for architectural outlines, floor guidance, commercial accents and decorative linear effects where a 100 mm control rhythm is acceptable.
It is not automatically the right choice for close-view media graphics, projects requiring a published walk-over rating, or installations where the available recess cannot accept the housing and cable route. Those conditions should be resolved before the sample is approved.
Information needed for quotation
Provide the total length and each control zone, installation section, main viewing distance, target animation, mounting orientation, controller information, cable entry direction, indoor or outdoor exposure, service method and required delivery date.
These inputs allow LIKELIGHT to evaluate pixel rhythm, data mapping, profile integration and sample configuration together. Power per metre, IP construction, white-channel specification and controller limits are not published on this page and must be confirmed for the selected production version.
Frequently asked questions
Is 10 pixels/m enough for a facade?
It can suit medium- and long-view movement, but the answer depends on distance, animation and fixture spacing; use a mock-up.
Does 60 LEDs/m mean 60 controllable pixels?
No. This product page lists 60 LEDs/m and 10 pixels/m as different quantities.
Can it be installed in a floor?
The page lists floor projects, but structural load, IP construction, drainage and cover details must be confirmed separately.
Is UCS2904 controlled like DMX512?
It is a cascade-pixel IC. DMX terminology applies only when a compatible upper-level system maps its pixel data.
What is missing before quotation?
Final length, zones, viewing distance, animation, controller, installation section, environment and cable direction are required.
