********* THE CONTENT OF THIS PAGE IS OUTDATED ***********

This guide covers the hardware and current Camera Server workflow for operating addressable NeoPixel LED strips from a Raspberry Pi with an XangleBoard. Treat the electrical ratings of the strip, board, and power supply as a separate hardware responsibility from Camera Server configuration.

Before you start

You need:

• A Raspberry Pi supported by the current XangleOS image and Camera Server network-node workflow.
• One XangleBoard per Raspberry Pi that drives a strip.
• A compatible addressable NeoPixel strip, such as a 5 V strip that accepts a single data signal.
• A suitable 5 V power supply sized for the strip's maximum pixel count and brightness.
• A separate USB-C or other supported power supply for the Raspberry Pi.
• A wired Ethernet connection or a reliable network path between the Pi and the Camera Server computer.

Do not use the old XCS16 version numbers as compatibility requirements. Check the current Camera Server release notes and the Network Nodes view for the supported Pi image and node versions before preparing a production rig.

Hardware installation

1. Power off the Raspberry Pi and disconnect its power supply.
2. Install the XangleBoard on the Pi's GPIO header. Make sure the header is aligned correctly and fully seated.
3. Connect the strip to the board's output terminals. Match the board labels to the strip:
   • GND to GND
   • DOUT to the strip's data input, usually marked DIN
   • 5VDC to the strip's positive 5 V input
4. If the strip provides a ground connection beside the data input, connect that ground as well. The wiring reference below shows the signal order and optional ground connection.
5. Connect the strip power cable to the correctly rated 5 V power supply. The LED power supply powers the strip, not the Raspberry Pi.
6. Power the Raspberry Pi from its own supported power supply.
7. Before connecting a long strip or turning on the full installation, verify polarity, the data direction, the voltage, and the power-supply rating.

The first pixel is directional. Connect the board's data output to the strip end marked DIN, IN, or with an arrow pointing toward the pixels. Connecting to DOUT can leave the strip dark even when the Pi and power supply are working.

Power and pixel limits

The maximum number of pixels depends on the strip, brightness, animation, wiring length, injection points, and power supply. Do not select a pixel count from an old shopping link or assume that one board can safely power any strip length.

• Size the 5 V supply for the strip's actual maximum current, with headroom.
• Use an appropriate fuse, distribution wiring, and power injection for longer strips.
• Keep the high-current LED power path separate from the Pi's power path.
• Never exceed the voltage specified by the strip.
• Start with a short test section and low brightness before connecting the complete installation.
• If pixels become dim, change color, flicker, or reset when the animation gets brighter, stop and investigate voltage drop or insufficient power before continuing.

The Pi can be installed near cameras or other rig hardware, but the LED supply must still be sized and wired for the strip. A shared Pi location does not make the LED power connection interchangeable with the Pi power connection.

Add the Pi in Camera Server

1. Launch the current Camera Server build.
2. Open the app's Network Nodes or node-management view and confirm that the Raspberry Pi is discovered.
3. Verify the node identity and connection state before assigning it to a production group.
4. Create or select the group that should control the light hardware, then assign the Pi to that group.
5. Open the lighting controls exposed by the current build for that group. Do not use the legacy http://localhost:8091/lights route as a required setup step.
6. Enter the number of active pixels and save the configuration.
7. Start with a simple color or pattern and confirm that the strip responds.

If the Pi does not appear, first check its power, Ethernet link, IP address, node image, and network visibility. A missing node is a discovery or network problem, not a strip pixel-count problem.

Configure patterns and capture behavior

Use the current lighting controls to create and save presets for the colors or patterns needed by the event. Keep a simple static preset available as a fallback.

Before enabling lighting changes during capture:

• Test the master light state from the operator controls.
• Test each preset with the complete strip connected.
• Confirm which group and node receive the command.
• Trigger a test capture and verify the light change occurs at the intended point in the sequence.
• Use the current trigger warmup or delay setting only when the hardware needs time to settle. Measure the required delay on the actual rig instead of copying a value from the old guide.
• Confirm the lights return to the intended state after a capture, error, app restart, or node reconnect.

Keep lighting control independent from camera triggering until both systems have passed separate tests. This makes it easier to tell whether a failed capture comes from the cameras, the network node, or the LED hardware.

Troubleshooting

The Pi is not discovered

Confirm that the Pi and Camera Server computer are on the same reachable network, that the Pi is powered, and that the Ethernet link is active. Restart the node only after checking the cable, switch port, and node identity. If other nodes are visible but this Pi is not, compare its image, network configuration, and power supply with a working node.

The strip stays dark

Check that the strip receives 5 V power, the grounds are connected, and the board data output goes to the strip's data input. Confirm the strip direction, pixel count, and selected group. Test a short section at low brightness to separate a wiring problem from a configuration problem.

The first pixels work but later pixels fail

Check voltage drop, power injection, cable size, connector quality, and the supply's current capacity. Reduce brightness and test again. A longer strip may need power injected at more than one point and may need to be divided across multiple power circuits.

The strip flickers or resets

Inspect the ground and data connections, shorten the data cable where possible, and verify that the LED power supply is not sagging under load. Do not solve repeated resets by increasing the configured pixel count beyond the physical strip.

A preset changes at the wrong time

Confirm the active group, preset assignment, and trigger warmup or delay settings. Test the preset manually first, then test it with one controlled capture before adding it to a full event sequence.