CONTROLLERS
Pixel Controllers Made Simple
Whether you're building your first display or expanding an existing one, the controller is the heart of your pixel network. Here we'll cover controller selection, setup, networking, receivers, port planning, power considerations, and real-world installation tips.
CHOOSING A CONTROLLER
Start With What Your Display Needs
Before choosing a controller, start with the display itself. How many pixels will you have? How far apart are your props? Will everything be close to the main controller, or will you need receivers in several locations? Answering these questions first makes choosing the right controller much easier.
PLAN BEFORE YOU BUY
Think about these four things first:
Pixel Count
How many total pixels will your display use?
Distance
How far are your props from the main controller?
Outputs
How many separate pixel connections will you need?
Expansion
Will you be adding more props or pixels later?
CONTROLLER TYPES
Understanding Your Controller Options
Pixel controllers come in several configurations, but they all serve the same basic purpose: getting data and power to your pixels. The right setup depends on whether your display is concentrated in one area or spread across multiple locations.
SHOW PLAYER
Show Player / FPP
A Raspberry Pi running Falcon Player (FPP) is often used as the show player. It stores the sequences and audio for the display, then sends show data across the network to one or more pixel controllers. The controllers receive that data and handle the actual pixel outputs.
PIXEL CONTROLLER
Controls the Pixels
The pixel controller receives show data over the network from FPP and converts it into the signals needed to control the pixels. Controllers such as the Falcon F16V5 provide local pixel outputs and can also send data to remote receivers located throughout the display
REMOTE RECEIVERS
Bring Outputs Closer to the Props
Remote receivers allow pixel outputs to be placed closer to props that are farther away from the main controller. A differential connection carries the control data from the main pixel controller to the receiver, helping reduce long pixel-data runs and making it easier to distribute outputs around a large display.
HOW IT ALL CONNECTS
From FPP to the Pixel
Your show starts with Falcon Player (FPP), usually running on a Raspberry Pi. FPP sends the show data across your network to the pixel controllers. The controllers then send pixel data directly to nearby props or through remote receivers positioned around the display.
RASPBERRY PI
Falcon Player (FPP)
Stores and plays the show
→
NETWORK
Ethernet
Carries show data across the network
→
PIXEL CONTROLLER
Falcon Controller
Receives show data and controls pixel outputs
→
REMOTE RECEIVER
Differential Receiver
Places pixel outputs closer to remote props
→
PIXELS / PROPS
Your Display
Pixels turn the data into light
CHOOSING YOUR HARDWARE
Picking the Right Controller for Your Display
Choosing a controller isn't just about the number of outputs. Consider your total pixel count, where your props are located, how far they are from the controller, how many remote locations you'll need, and how much you expect the display to grow in the future.
PIXEL COUNT
Know Your Total
Estimate how many pixels your display will use and how they will be divided among your props. This helps determine how many controller outputs you need and how much capacity to leave for future growth.
PHYSICAL LAYOUT
Map Out Your Props
Think about where each prop will be located and how far it will be from the controller. Grouping nearby props together can simplify wiring, reduce long pixel runs, and help determine where controllers or remote receivers should be placed.
REMOTE LOCATIONS
Plan for Distance
If your display is spread across several areas, remote receivers can place pixel outputs closer to the props. Plan where those remote locations will be and how they will connect back to the main pixel controller.
FUTURE EXPANSION
Leave Room to Grow
Plan for more than what you need today. Leaving extra controller outputs, receiver capacity, and room in your network makes it much easier to add new props and pixels as your display grows.
CONTROLLER PLANNING
Main Controllers vs. Remote Receivers
A good controller layout keeps pixel connections reasonably close to the props they control. Some props can connect directly to the main controller, while others may be better served by remote receivers placed around the display. The goal is to reduce long pixel runs while keeping the system organized and easy to expand.
MAIN CONTROLLER
Direct Pixel Outputs
Props located near the main controller can connect directly to its pixel outputs. This works well when several props are grouped in the same area and keeps the setup simple by eliminating the need for additional remote receivers.
REMOTE RECEIVER
Outputs Closer to the Props
Remote receivers are useful when props are farther away from the main controller. They place pixel outputs closer to those props while a differential connection carries the control data from the main controller to the receiver.
PORT PLANNING
Plan Your Outputs Before You Wire
Good port planning makes a display easier to wire, troubleshoot, and expand. Instead of simply filling each controller output with as many pixels as possible, think about which props are located near each other, how many pixels each prop uses, and how the wiring will run through the yard.
GROUP NEARBY PROPS
Keep Wiring Simple
Group props that are physically close together on the same controller outputs whenever practical. This can reduce long cable runs, simplify wiring, and make troubleshooting much easier.
WATCH PIXEL COUNTS
Balance Your Outputs
Keep track of how many pixels are assigned to each output. Spreading the load sensibly across the controller can make your layout easier to manage and helps avoid putting too much of the display on a single output.
LEAVE ROOM TO GROW
Don’t Use Every Output
Leave some controller capacity available for future props and changes. A little extra room now can save you from having to redesign your controller layout when the display grows later.
POWER PLANNING
Power Your Pixels the Right Way
Power planning is just as important as data planning. As pixel counts increase and cable runs get longer, voltage drop and power demand become more important. Plan your power supplies, wire sizes, fusing, and power injection points before installation so your pixels receive reliable power throughout the display.
POWER SUPPLIES
Plan for the Load
Choose power supplies with enough capacity for the pixels they will support, while leaving some extra capacity rather than operating them at their maximum rating. Divide the display into manageable power zones so each supply serves a sensible group of props.
FUSING & WIRE
Protect Every Circuit
Use properly sized wire and appropriate fusing for each power circuit. Fuses help protect the wiring if a short or overload occurs, while the correct wire size helps reduce voltage drop and keeps power delivery reliable.
POWER INJECTION
Keep Voltage Consistent
Long pixel runs or large props may need additional power farther down the line. Power injection supplies fresh power at strategic points to help reduce voltage drop and keep pixel brightness and colors consistent throughout the prop.
NETWORKING
Connecting the Show Together
Your show network connects Falcon Player (FPP) to the pixel controllers that run the display. FPP sends show data over Ethernet to the controllers, while your network switches and cabling provide the path between them. A well-planned network keeps communication reliable and makes it easier to add controllers as your display grows.
SHOW PLAYER
Falcon Player (FPP)
FPP is the starting point for the show. It plays the sequences and audio, then sends the show data across the network to the pixel controllers at the correct time.
NETWORK SWITCH
Connect the Network
An Ethernet switch provides the connection between FPP and multiple pixel controllers. It gives each network device a reliable wired path for show data and makes it easier to expand the network as more controllers are added.
PIXEL CONTROLLERS
Receive the Show Data
Pixel controllers receive the show data from FPP over the network and convert it into the signals needed by the pixels. Each controller can handle its local outputs and, when supported, send data to remote receivers located around the display.
REAL-WORLD CONTROLLER LAYOUT
How the Pieces Work Together
A typical display uses several pieces working together rather than one controller doing everything. Falcon Player starts the show, the network carries the data, the main controller handles local outputs, and remote receivers extend those outputs closer to props located farther away.
MAIN CONTROL AREA
FPP + Network + Controller
Falcon Player runs the show and sends data through the network to the main pixel controller. Props located nearby can connect directly to the controller’s local pixel outputs.
REMOTE AREA
Differential Receiver
When props are farther from the main controller, a differential connection carries control data to a remote receiver. The receiver places pixel outputs closer to that part of the display, reducing the need for long pixel-data runs.
PROPS
Pixels Bring It to Life
Trees, arches, snowflakes, outlines, and other props connect to the nearest available pixel outputs. Planning controller and receiver locations around the props helps keep wiring shorter, cleaner, and easier to troubleshoot.
MY CONTROLLER SETUP
What Powers Lights in the Swamp
Lights in the Swamp uses a distributed controller setup designed to keep pixel outputs close to the props they control. The system combines a central show player, networked pixel controllers, and remote receivers positioned throughout the display. As the show grows, this setup makes it easier to add new props without rebuilding the entire control system.
SHOW PLAYER
Falcon Player (FPP)
Falcon Player runs the Lights in the Swamp show, handling the sequence playback and audio while sending show data across the network to the pixel controllers.
MAIN CONTROLLER
Falcon F16V5
The Falcon F16V5 serves as the main pixel controller for Lights in the Swamp, receiving show data from FPP and distributing it to local pixel outputs and remote locations throughout the display.
REMOTE RECEIVERS
Distributed Around the Display
Remote receivers are positioned closer to groups of props around the display, allowing pixel outputs to be distributed where they are needed while keeping long pixel-data runs to a minimum.
LEARN MORE
Keep Building Your Display
As Lights in the Swamp continues to grow, I’ll be adding more detailed guides covering controller setup, Falcon Player, networking, remote receivers, power planning, and other lessons learned from building the display.