The short answer
Identify the exact LED SKU and revision, then obtain its topology, pinout, IC and protocol. Match those to the controller's real output—not merely its input label—and check voltage, per-channel or pixel capacity, addressing, colour order, data wiring, power injection, environment and saved configuration. If any protocol field is unknown, treat compatibility as unconfirmed and run a short, current-limited sample using manufacturer instructions.
1. Decide whether the load is analogue RGB or addressable pixel
In a conventional constant-voltage RGB strip or module, the red, green and blue channels for a connected branch are normally controlled together. The controller modulates those power channels, so every LED on that output follows the same colour command. Check whether the load is common-positive or common-negative, the rated voltage and the current for each channel; the word RGB alone does not supply those answers.
In an addressable system, data reaches an IC associated with an individual pixel or defined group. The controller must generate the exact supported protocol and the wiring must follow the specified data direction, logic and reference arrangement. Addressability, pixels per group and colour order are product properties or configured behaviours, not assumptions that follow from the words digital or programmable.
Keep input and output interfaces separate. ENTTEC's CVC4 can receive DMX/PLINK and drive four constant-voltage channels for RGB/RGBW. Its DMX input does not turn the connected strip into addressable pixels. Conversely, a pixel controller such as DIN Pixie selects a specific pixel protocol. Write both sides of the controller in the matrix.
| System question | Analogue constant-voltage RGB | Addressable pixel RGB |
|---|---|---|
| What varies independently? | The controller's R/G/B power channels for a branch | Each supported pixel or configured group |
| Critical LED evidence | Voltage, common polarity, pinout, channel current | Voltage, pinout, IC, protocol, direction, timing/logic, colour order |
| Controller output to verify | Channel voltage/current and total capacity | Supported protocol and physical pixel/output capacity |
| Typical configuration record | Input mode/address and channel mapping | Protocol, pixel order, grouping, start address, loss behaviour |
| Do labels prove compatibility? | No: DMX may be input only | No: digital does not identify IC or protocol |
2. Complete an RGB system compatibility matrix
Begin with the required effect and granularity. A static colour wash or whole-sign fade may not need per-pixel control; a chasing border or mapped animation does. State the smallest element that must change independently and the required update behaviour. This avoids purchasing pixel equipment for an analogue effect—or an analogue decoder for a pixel effect.
Name the LED or module manufacturer, exact SKU and hardware revision. Record voltage, current or power by colour where supplied, conductor count, connector, pinout, common polarity or data line, IC, protocol/version, data direction, backup line, logic level or baud/timing, colour order, channels per pixel and any fixed grouping. A blank cell is a blocker, not permission to substitute a familiar WS281x value.
Name the controller/decoder model and firmware. Record its input protocol, output type, compatible pixel protocols or CV channels, start address/universe, per-channel current, total current, physical pixels per output, input-channel budget, refresh limit and fail-state. ENTTEC lists 5 A per channel and 20 A total for the CVC4 model 73926; those figures illustrate why both limits matter, but they apply only to that exact decoder and do not prove suitability for a Glowfy module.
3. Treat saved configuration as part of the product
A compatible controller can still produce wrong colours or no output if the configuration is different. The DIN Pixie documentation exposes settings including DMX personality and start address, pixel protocol, pixel order, grouping and behaviour on DMX loss or blackout. Export or photograph the actual configuration used for the approved sample and attach the firmware version.
Pixel grouping reduces the number of input channels required to command a larger set of pixels together. ENTTEC explicitly notes that grouping does not increase the controller's physical pixel output capacity. Keep pixels per group, DMX/input-channel budget and physical output capacity as three separate rows. Do not use grouping to justify a longer electrical chain.
ANSI E1.11-2024 defines DMX512-A data transmission between controllers and lighting equipment. It is not a generic name for every internal LED signal. If a controller receives DMX and then generates a pixel protocol, record both interfaces and their mapping. If it receives Wi-Fi instructions and outputs analogue PWM channels, record that different topology instead.
| Matrix row | Required evidence | Reject or escalate when |
|---|---|---|
| Effect and granularity | Whole branch, pixel or group; expected scenes | Effect requires independent elements the load cannot address |
| LED interface | Exact voltage, pinout, IC/protocol, direction and colour order | IC/protocol or conductor function is undocumented |
| Controller output | CV channel limits or supported pixel protocol/capacity | Only the controller input is named |
| Addressing and grouping | Universe/start address, channels/pixel, pixels/group | Channel budget is confused with physical output capacity |
| Data link | Cable type/length, reference, branching, termination/buffering | A generic cable length is assumed without system documentation |
| Power and environment | Supply/injection/fusing; connector and enclosure/IP limits | Module IP rating is transferred to controller or joints |
| Configuration evidence | Firmware and exported/screenshot settings | The approved behaviour cannot be recreated |
4. Engineer power and data as linked but separate paths
Calculate the connected load from manufacturer data and check the supply voltage, continuous capacity, branch conductors, connectors and protection. For analogue RGB, verify both the worst channel and combined decoder limits. For pixels, include the documented full-output condition and follow the manufacturer's injection rules. Do not infer full-white current from a different IC family or from a visual test.
Route data according to the controller and pixel instructions. Record the common reference or ground, cable type, permitted length, branch topology, direction arrows, termination or buffering and any maximum chain. Power injection can correct voltage distribution; it does not regenerate an unsupported or degraded data signal. A star branch that is acceptable for power may be invalid for a one-way pixel data chain.
Environmental ratings also remain separate. The Glowfy module listing gives IP67 for the module, while ENTTEC describes DIN Pixie as IP20 and unsuitable for moisture or condensation. The installed system must protect the controller, supply, connectors, cable entries and data joints for their locations. Never transfer the module's IP rating to the enclosure.
5. Read the current Glowfy RGB listing conservatively
Glowfy's current GF-PRO-RGB-12V page identifies a product titled RGB DIGITAL PRO with 12 V input, 0.72 W rated power, RGB output, 120° beam angle, IP67 and dimensions of 71 × 15 mm. It says a compatible RGB controller is required. These are useful ordering facts, but they do not disclose the control interface needed for a controller decision.
The public listing does not identify the IC, protocol, conductor count, pinout, common polarity or data line, addressability, logic/timing, colour order, maximum chain, data distance, injection rules or a verified controller SKU. The page's references to Wi-Fi RGB and a four-channel DMX512 RGBW controller are not a published compatibility declaration for this module. The checked 28-product catalogue also showed no standalone controller listing.
Therefore do not promise independent pixel animation, DMX compatibility or a WS2811/WS2812 interface from the DIGITAL name. Request the current module and controller documentation, photographs of the conductors and labels, and written confirmation of the output interface. If those details remain unavailable, restrict the decision to a controlled sample and label the system unconfirmed rather than guessing.
6. Run a short, controlled compatibility sample
Use a short representative branch and a current-limited supply configured according to the manufacturers' circuit instructions. Confirm polarity and pinout before energising. Load the documented controller configuration rather than a convenient default. Record LED/module revision, controller model and firmware, power supply, wiring diagram, cable length and configuration export.
Command red, green and blue separately to confirm channel or colour order, then test the required mixed colours and effect. For pixels, observe the first and last pixel, grouping boundaries and restart behaviour. Test the documented response to data loss and restoration. Record full-output current with suitable equipment, voltage at relevant points, visible flicker or camera artefacts, connector and component temperature, and recovery after a representative joint or pixel fault only where the manufacturer permits that test.
Approve or reject against the required effect and the matrix. An apparent colour response is not enough if the controller exceeds a current limit, the last pixels corrupt, the configuration cannot be restored or the environmental enclosure is unresolved. Scale-up needs a documented branch, power-injection and data-distribution design; the short sample does not silently approve an unlimited chain.
| Sample step | Record | Pass condition |
|---|---|---|
| Identity and wiring | Exact labels/revisions, pinout, direction and diagram | Matches current manufacturer evidence |
| Colour order | Separate R, G, B commands and mixed colour | Mapping is correct and reproducible |
| Required effect | Granularity, grouping, first/last element | Effect works across the representative branch |
| Power check | Supply setting, full-output current and point voltages | Within documented component and wiring limits |
| Data-loss/restart | Fail-state, power cycle and restoration | Behaviour matches the project requirement |
| Handover | Firmware and configuration export | Another technician can restore the approved state |
7. Worked example: a DMX label does not settle the output type
Illustrative example, not a Glowfy test result: a sign brief calls for DMX control and animated colour along a border. Supplier A proposes a DMX-to-CV RGB decoder. It can receive the building's DMX signal, but every module on each RGB branch changes together. The decoder meets the input requirement but not the requested per-pixel granularity.
Supplier B proposes a DMX-input pixel controller, yet the LED module sheet says only RGB digital. The project still lacks the module IC, protocol, pinout and colour order, so controller compatibility remains unconfirmed. The team requests those fields and builds a short branch only after the output protocol is matched.
The approved schedule finally names both interfaces: DMX universe and start address on the input, then the exact pixel protocol, order, grouping and capacity on the output. It also names supply branches, injection points, data cable and enclosure. This prevents the word DMX from concealing two different engineering decisions.
Frequently asked questions
Does DMX mean the connected RGB LEDs are individually addressable?
No. DMX may control a decoder whose output is three or four constant-voltage channels. Check the controller's output interface and the LED topology.
Can I identify a pixel protocol from the word digital?
No. Obtain the exact IC, protocol/version, pinout, signal requirements and colour order for the LED SKU and revision.
Does pixel grouping let a controller drive more physical pixels?
No. Grouping reduces the number of input channels used to command pixels together; it does not increase the controller's physical output capacity.
What evidence should I send for an RGB compatibility review?
Send photos of labels and conductors, the LED and controller datasheets, exact revisions, required effect, wiring distances, power design, environment and the saved controller configuration.
Technical references
Use the current datasheet for the exact product you install. These manufacturer and standards resources explain the general principles.
Verify the RGB interface before scaling up
Send the LED and controller labels, conductor photographs, protocol sheets and required effect for help identifying the evidence missing from a compatibility sample.