A good shopping list starts with what you want to build and ends with how every piece connects. Pixel counts matter, but so do the cable that reaches the first node, the correct connectors, the mounting hardware and the power needed at the far end.
Here is our workflow for turning a rough xLights layout into an order you can check. The numbers below are an illustrative planning example, not a pre-engineered kit or an electrical rating.
1. Name and count the actual props
In the Layout tab, give each physical item a useful name: Window_Left, Window_Right and Roof_Lower are easier to follow outside than three copies of Model1. Match the selected model to the product, including its node count, starting point, direction and any folds. Save the layout before exporting it.
Use Tools > Export Models to create the model spreadsheet. Keep a clean copy, then make a working sheet for your order. Review the rows so groups, alternative previews or duplicate representations of the same lights do not become extra physical purchases.
Separate lights already included in an assembled prop from empty props that need pixels. Also separate RGB pixel nodes from equipment such as moving heads. A fixture's DMX channels are not a quantity of replacement pixels.
2. Fill a worksheet before choosing quantities
This example assumes two measured window outlines with 80 nodes each and one roof section with 200 nodes. All three use the same selected 12V, three-wire pixel and connector family. The cable lengths include the planned route and service slack; they are example measurements, not recommended maximum distances.
Scroll sideways to see all columns.
| Physical item | Nodes | Planned output | Cable needed | 100-node strings allocated |
|---|---|---|---|---|
| Window_Left | 80 | Controller A, port 1 | 8 ft | 1 |
| Window_Right | 80 | Controller A, port 2 | 13 ft | 1 |
| Roof_Lower | 200 | Controller A, port 3 | 18 ft | 2 |
| Total | 360 installed | 3 planned outputs | 3 cable routes | 4 strings / 400 purchased nodes |
Four 100-node strings supply 400 nodes. If the selected pixel product permits shortening and you accept its modification and warranty conditions, shortening both window strings to 80 leaves 40 nodes for other work or repairs. Those offcuts are not automatically ready-to-plug spare strings: account for termination, connectors and weather sealing. If you prefer no cutting, select suitable finished lengths and change the order quantities accordingly.
Add columns for voltage, protocol, connector at each end, string length, mounting method, power arrangement, exact variant and quantity already owned. Do not assume two products are interchangeable because both descriptions say “100 pixels.”
3. Assign controllers by location and capability
Place each controller or receiver where it serves a sensible part of the display. Choose the actual hardware in xLights. With a supported controller and Auto Layout Models enabled, its Visualise view lets you assign models to outputs. Resolve any reported configuration errors.
Our three-output sketch is only a data-routing plan. Before ordering, check the selected controller's pixel protocol, per-output current, total bank limits, channel capacity, supported frame rate and receiver compatibility. Check the power supply, wire and connector ratings separately. An available port does not prove that the connected load is acceptable.
For distant props, compare a properly supported receiver arrangement with long pixel cables. There is no cable distance that works for every combination of pixels, controller, wire and environment.
4. Measure the route the cable will follow
Use Tools > Export Controller Connections for the hookup sheet, then walk the layout. Measure from the actual controller position to the actual data input, including vertical sections, corners and any protected route around doors or paths.
If a measured route needs 13 feet, choose an available cable or combination that reaches with useful slack. Record the exact connectors and direction of every adapter. Keep three-wire and four-wire systems distinct. Add only the adapters the final connection actually needs.
Label both cable ends with the same prop and port names used on the worksheet. This small step makes setup, troubleshooting and storage easier to repeat.
5. Add everything that the node count missed
- Power: correctly matched supplies, rated distribution, suitable fusing and any required injection wiring.
- Physical installation: mounting strips or tracks, approved supports, fasteners and the specific hardware needed for your surfaces.
- Connections: extension cables, appropriate pigtails, output caps and rated splice materials where required.
- Playback: your chosen computer or show player, network connections and audio equipment.
- Maintenance: compatible spare pixels, correct spare fuses, labels and storage containers.
Separate equipment already owned from new purchases. Carry quantities and prices by exact variant; avoid adding a “from” price for one option to a description of another.
6. Finish with one complete test connection
Before repeating the build across the house, assemble one representative path: controller, planned extension, first prop and its intended power arrangement. Verify voltage and polarity before energizing it. Test colors, node count, direction and operation at the planned brightness using a power plan suitable for that test.
Update the worksheet when anything changes. Your final order, xLights layout and cable labels should describe the same display. For the next step, use our project budget examples or window-frame guide.
References
Put the guide to work
Download the editable planning workbook and bench sheets, then review the selected variants in Build This Project. Keep equipment you already own in the plan even when it is left out of the shopping list.
Using EZRGB for design or mapped content?
The Light Show Designer planning guide explains how to keep the visual design and physical installation plan together. Use EZSequence layout mapping for the content side, and verify the controller port plan separately.
