Control System
The Falcon F48V5 sits at the center of the installation, sending pixel data over Cat6 cable to SmartReceivers distributed throughout the structure.
Architecture
Falcon F48V5 (main controller)
│
└── Cat6 runs to SmartReceivers (one per zone cluster)
Each SRx drives up to 16 output ports
For software and show design, see Light Show Design.
Hardware
| Item | Details | Source | Price |
|---|---|---|---|
| Falcon F48V5 | 48 differential outputs over Cat6; 192 universes | pixelcontroller.com | $270 |
| SRx4 SmartReceiver | 4-in-1, 16 outputs — one per tower | pixelcontroller.com | $90 |
| SRx1 V5 (preferred) | Single SmartReceiver, 4 outputs — rose window (one petal per port) + tower corners | buildalightshow.com | $40 |
| SRx1 V4 (fallback) | In stock at pixelcontroller.com | pixelcontroller.com | $35 |
15 SmartReceivers total: 4× SRx4 (one per tower), 8× SRx1 (4 rose window + 4 tower corners), 3× SRx2 (arches). See wiring.md SR count summary.
The F48V5 supports 192 universes across its 48 differential output ports — universes and outputs are not 1:1. The full installation uses universes up to u75, well within capacity.
Universe assignments
Updated 2026-07-12/13. Major arches went full-resolution and moved to the tail; the towers relocated for the chained quads; the interior orbs were cut. Canonical source: universe-map.json and wiring.md.
| Zone | Universes | Notes |
|---|---|---|
| Rose window (design / cell level) | 1–2 | 8 petals × 14 cells × 3 ch per universe. Physical-pixel expansion (~517/petal) is generated by an offline FSEQ post-processor and lives in universes u76–u139. |
| Minor arches | 7–16 | 10 arches |
| Major arches | 39–48 | Full resolution — every WS2811 pixel (~216–233 px/arch), grouping = 1. Each arch gets a 2-universe block. |
| Towers — spires, spirelets, canopy, chained quads | 50–75 | Relocated from u17–u38 (2026-07-12). Each quad is one chained data string. |
| Vacated | 3–6, 17–38, 49 | Free for reuse (e.g. wash floods) |
Universe usage
The F48V5 supports 192 universes and can drive up to 32,768 pixels — the design uses universes up to u75 (with the rose-window physical expansion reserved for u76+). The constraint is physical wiring topology: each independent strip run or string needs its own universe start channel, and zone boundaries (petals, arch segments, spire strings) can’t be daisy-chained across physical gaps. The 192-universe capacity gives ample headroom.
Modes
| Mode | Description |
|---|---|
| Unattended / ambient | xLights sequences played back by FPP autonomously — fire, pulse, twinkle, cathedral glow. No operator needed. |
| Sequenced show | Pre-programmed sequences designed in xLights, played back via FPP in sync with music. |
| Live reactive | TouchDesigner responding to sound/BPM in real time. Requires a collaborator on-site. |
Software stack
| Tool | Role |
|---|---|
| xLights | Sequence design on laptop; exports to FPP for playback |
| FPP (Falcon Player) | Runs on the F48V5; plays back xLights sequences; handles unattended show |
| TouchDesigner | Live reactive control, driven by sound/BPM. |
| Ableton Link | BPM sync from nearby art cars into TouchDesigner |
Data flow
Unattended / sequenced:
xLights render ──► expand/compress (rose u76–u139 + 8 kW budget) ──► FPP ──► F48V5 ──► SmartReceivers ──► LEDs
Live reactive:
Ableton Link (BPM)
│
TouchDesigner ──► F48V5 ──► SmartReceivers ──► LED strips/nodes
During development, a relay server on the laptop intercepts sACN from TD or xLights and forwards it to the browser simulator. On playa, the same sACN goes straight to the F48V5 — nothing else changes.