Eos Lightmedia · Hardware

Eos Pixel Driver

Embedded pixel control for permanent installations. No PC. No network. No single point of failure. Wire it, power it, leave it — it runs at 60 fps, unattended, for years.

Wire it. Power it. Leave it.

A standalone controller that just runs

The Eos Pixel Driver generates and outputs real-time lighting scenes directly on-device. Drop a scene file onto it over USB, wire it to your fixtures, and walk away.

Pixel Driver board mounted in an enclosure, wired to a pixel ring
Standalone operation

No media server. No operating system. No moving parts.

Scene generation runs directly on the embedded processor. There is no Windows box in a closet to reboot, no GPU driver to update, no license server to maintain. Power it, and it runs. That is the entire operations model for a permanent installation.

Pixel Driver connected via USB-C with status LEDs lit
Scene loading

Drag and drop.

Connect via USB-C and the device mounts as a standard drive. Drop a scene file onto it, reset, and the new scene is running. Firmware updates work the same way — no proprietary software, no flashing tools, no special procedure.

Pixel Driver on a bench with sensors and probes attached
External control

Standalone, but not isolated.

Two 0–5 V analog inputs accept signals from sensors, potentiometers, or control systems. A serial port accepts commands from PLCs, touch panels, and media servers. The driver runs its scene autonomously while external signals shape the behavior. Upstream goes quiet? The show still goes on.

Pixel Driver installed in a clear case driving an LED strip
On-board diagnostics

Read the board at a glance.

On-board status LEDs give real-time feedback without tools. Power glows steady blue. Render speed reads green at 60 fps, shifting toward red to show computational demand. Input levels read from blue to red as voltage rises.

Output protocols

Speaks the protocol your fixtures speak

A few of the protocols supported today. The list keeps growing — because we own the firmware, new protocols get added as the jobs require.

WS2812 / WS2812B

NeoPixel · TTL

Single-line addressable RGB. The most commonly found pixel protocol today.

SK6812

RGBW Addressable

Four-channel output with dedicated white for warmer tones and higher CRI in architectural applications.

DMX512 · RS485

DMX

Full universe output via UART adapter. Compatible with legacy and high-end stage fixtures.

APA102 / SK9822

Dual-Line SPI

Separate clock and data lines for high refresh rates and reliable timing over long cable runs.

…and more on request.

Application examples

One driver, many installations

Permanent installations

Set-and-forget lighting for lobbies, facades, and public spaces. Runs unattended for years without intervention.

Interactive displays

Sensor-driven scenes that react to motion, proximity, or manual controls. Real-time input, real-time light.

Hybrid control

A show controller or PLC sends high-level commands. The driver handles scene generation locally, cutting network and graphical load.

Hardware version 1.5

Technical specifications

Processor

Architecture
Dual-core ARM Cortex-M0+
Clock speed
Up to 133 MHz flexible clock
Memory
264 kB SRAM

Power

Input voltage
5–24 V DC
Input protection
Reverse-voltage protection, 8 A resettable fuse
Power consumption
0.15 W 0.03 A @ 5 V · 0.01 A @ 12 V
LED output power
Pass-through output voltage matches input
Logic voltage
5 V sensor power · 3.3 V GPIO

Performance

Render rate
60 fps target configurable
Master brightness
0.0–1.0, software-controlled
Gamma correction
Configurable exponent, default 2.0

Connectivity

Power input
3.81 mm Phoenix, GND / VIN 16–28 AWG
LED output
3.81 mm Phoenix, GND / DAT / CLK / VCC 16–28 AWG
Front I/O
2× 5 V ADC, 3.81 mm Phoenix GND / ADC / +5V
Side I/O
1× 3.3 V ADC/GPIO · 2× GPIO · Reset screw terminal, 14–30 AWG
Data port
USB-C USB 1.1, device + host

Firmware & storage

Scene files
USB-C drag-and-drop .cndl format
Firmware update
USB-C bootloader mode drag .uf2
Configuration
settings.json on device auto-generated on first boot
We own the full stack

We design the board. We write the firmware. We build whatever the project needs.

The Eos Pixel Driver is not an off-the-shelf controller with fixed capabilities. Because Eos Lightmedia owns the hardware and the software, every aspect of the platform can be tailored to your installation — from custom IO to audio-reactive effects.

3rd-party modules FFT / audio analysis Tone generation I2C / SPI peripherals Custom protocols
Talk to Eos Lightmedia