What an SPI pixel controller does
Console / show controller → Art-Net or sACN network → SPI pixel controller → addressable LED tapeArt-Net and sACN transport DMX-style channel values over an Ethernet network. Addressable tape does not normally understand those network packets directly. The pixel controller maps incoming universes and channels to pixels, then produces the tape's low-level data—and sometimes clock—signal.
The same device may be described as an SPI decoder, pixel decoder, pixel controller, eDMX-to-pixel controller, or network-to-SPI converter. Product terminology varies; the important question is what data it receives and what electrical signal it outputs.
SPI does not mean every tape uses the same protocol
“SPI” is often used as an umbrella term for pixel output, but WS2812B-style one-wire timing, APA102-style data-and-clock signaling, backup-data tape, and other IC families are not automatically interchangeable. The controller's supported pixel list must include the exact IC or a manufacturer-approved compatible mode.
Do not select a controller only because it says SPI. Confirm the IC protocol, RGB/RGBW/RGB+CCT channel format, color order, bit depth, data rate, and whether a clock or backup-data conductor is required.
How many universes and pixels do you need?
A standard DMX universe contains 512 channels. An 8-bit RGB pixel uses three channels, RGBW uses four, and RGB+CCT may use five. Because a pixel cannot be split cleanly across a universe boundary in many workflows, practical capacity is commonly treated as 170 RGB pixels or 128 RGBW pixels per universe.
Pixel data channels = controllable pixel groups × channels per pixel Universes required = ceiling(pixel data channels ÷ 512)Use controllable pixel groups—not physical LED count—when the tape groups several LEDs under one IC address. Also verify the controller's per-port pixel limit, per-port universe limit, total device capacity, and maximum refresh rate. A large headline pixel count may depend on color format, bit depth, output timing, or distributing pixels across multiple ports.
The seven most important selection criteria
- Input protocol: match Art-Net, sACN, DMX512, KiNET, or the source protocol used by the show system.
- Pixel protocol: verify support for the precise IC family and required data/clock arrangement.
- Color format: confirm RGB, RGBW, tunable white, RGB+CCT, color order, and 8- or 16-bit handling.
- Capacity: check total universes, outputs, pixels per port, and the achievable update rate at the planned load.
- Signal distance: raw pixel data is distance-sensitive. Place the controller near the first pixel or use a supported differential extender or satellite system.
- Power topology: determine whether the device passes pixel power, provides fused outputs, or outputs data only. Size power supplies, conductors, connectors, and branch protection separately.
- Commissioning tools: web configuration, test patterns, universe identification, pixel grouping, reverse direction, brightness limits, diagnostics, and configuration backup can save substantial field time.
Keep raw SPI runs short
The electrical data output to the tape is not Ethernet. It is typically an unbalanced, timing-sensitive signal that can degrade through long cable runs, poor grounding, electrical noise, or unsuitable cable. Manufacturer limits vary by product and protocol, so follow the controller documentation rather than applying a universal distance.
For long distances, move the pixel controller closer to the tape or use a manufacturer's differential transport system. Examples include ENTTEC's PLink architecture and Visual Productions' SpiExtender approach. These carry a more robust signal over structured cable and convert back to local pixel data near the LEDs.
Pixel power and controller power are separate
Some controllers have powered and fused pixel outputs; others generate data only. Even when power passes through the controller, its terminal, fuse, and per-port current ratings may be far below the total current required by a long tape installation.
Power injection can feed the tape at additional locations without routing the full LED load through the controller. The controller and pixels still need the correct signal reference, and every power branch needs conductor and overcurrent protection appropriate to its load.
Read the wiring diagram for the exact device. “5–24V input” may describe only the controller's own supply range; it does not automatically mean every pixel output can safely distribute the project's full LED current.
Representative professional product approaches
| Manufacturer | Representative approach | Useful distinction |
|---|---|---|
| ENTTEC | OCTO family for direct network-to-SPI output; Pixelator/PLink architecture for distributed installations | Direct local SPI and long-distance satellite-style options are separate system designs |
| Advatek | PixLite Mk3 network pixel controllers | Broad pixel-protocol support, powered/fused output options, and configuration/diagnostic tooling |
| Visual Productions | SpiNode with optional SpiExtender | DIN-rail Art-Net/sACN-to-SPI conversion with a differential extension option |
| DMXKing | LeDMX/eDMX MAX pixel-output devices | Art-Net/sACN mapping, configurable pixel types, color order, timing, and playback/failover features depending on model |
| Pharos | Designer controllers as show-control and eDMX sources; SPI through supported EDN/RIO plus SDI hardware or third-party pixel controllers | Pharos often supplies the programmed lighting data rather than serving as a standalone tape-side decoder |
These are examples of system architectures, not a ranked buying list. Product capacities and supported protocols change by model and firmware; verify current manufacturer documentation before specifying hardware.
Example system layouts
Small local installation
Lighting software → Ethernet switch → 4-port pixel controller → short SPI leads → tape + local power injectionDistributed architectural installation
Pharos or other show controller → managed lighting network → pixel controllers near each LED zone → local PSUs and protected branchesController far from the LEDs
Art-Net/sACN source → master pixel controller → differential link over Cat cable → receiver/injector near tape → short SPI leadCommissioning checklist
- Confirm tape voltage and pixel IC from the product datasheet.
- Count IC-controlled pixel groups and channels per group.
- Patch the correct starting universe and channel for every output.
- Set the correct RGB color order and direction.
- Use built-in test patterns before troubleshooting the network source.
- Verify common signal reference and manufacturer grounding instructions.
- Measure voltage at the first and last pixels under full white or maximum load.
- Test loss-of-data, restart, and failover behavior before handover.
- Save and document the final controller configuration.
Size the pixel load first
Use the calculator to estimate connected load, current, power supplies, voltage drop, injection points, pixel groups, and data-channel count before selecting controller capacity.
Open LED Tape CalculatorRelated guides
Sources & further reading
- ENTTEC — LED pixel controller families and PLink architecture
- ENTTEC — OCTO Mk3 configuration and mapping
- Advatek — PixLite A4-S Mk3
- Visual Productions — SpiNode and SpiExtender
- DMXKing — eDMX MAX configuration manual
- Pharos — Designer VLC output architecture
- Pharos — Advatek PixLite Mk3 integration
Planning disclaimer
This guide is for project planning and education. Verify capacities, supported protocols, wiring, power limits, environmental ratings, and safety requirements against current manufacturer documentation for the exact hardware and tape.