To daisy-chain DMX lights, connect the controller’s DMX OUT to the first fixture’s DMX IN. Continue from that fixture’s OUT or THRU to the next fixture’s IN, using the ports identified in each manual. Terminate the last physical end with a suitable plug or the device’s documented internal termination, not both.
That cable route carries control data. It does not supply operating power, and placing a fixture first does not automatically give it the first DMX address. Keep three questions separate: where does the cable go, which channels should each light read, and how is each fixture powered?
A useful setup method answers those questions before the whole rig is connected. Start small, confirm a deliberate response, and extend the route while you can still identify what changed. This guide draws on manufacturer documentation and develops that method into a practical connection and fault-finding procedure. Begin by identifying the equipment you will actually connect.
Prepare the data path before connecting lights
Before laying out the complete route, gather the manuals and make a short fixture list with each light’s position, selected DMX mode and intended start address. This gives you something definite to compare with the controller when a light responds incorrectly.
Prepare four things:
- Signal Source: Identify the DMX output you will use and how to enable it. When checking a dmx controller, distinguish its physical output from the fixture settings in its patch. Both matter; finding the right socket does not confirm the programming.
- Data Cable And Termination: Use suitable DMX data cable and the termination method specified for the endpoint. Matching connector shells prove only physical fit. If browsing stage lighting accessories, compare the item’s documented purpose with your equipment rather than choosing by appearance.
- Fixture Settings: Find the DMX input and output or through connection. Select the intended DMX mode, not an automatic program that could produce activity without following your commands.
- Power And Test Conditions: Treat operating power separately and follow each manual’s power-link limits. Arrange a controlled test under venue rules, with movement and beam paths managed before enabling output. Follow the equipment’s connection procedures rather than assuming one power-up sequence suits every rig.
Keep a verified reference cable and source available where possible. “Known-good” means they have demonstrated the intended response together, not simply that the cable is new. If an unverified spare fails too, you have added another uncertainty rather than isolated the first problem. The aim is to establish one clear response you can return to before adding more possible failure points.
Build the chain from one tested connection
The CHAUVET DMX Primer describes the basic output-to-input connection. Build on that simple route by checking a deliberate response at each stage:
- Connect One Fixture: Run the source output to its DMX input. At this stage, that fixture is also the end of the line, so use its appropriate termination method. Leave the rest of the planned data route out of this first check.
- Match The Settings: Compare the controller’s fixture profile, the light’s selected mode and its start address. A profile describes how the controller maps commands to that fixture’s channels. A correct cable cannot make a mismatched map produce the functions you expect.
- Choose A Simple Look: Use the exact fixture chart to identify the settings needed for a controlled visible response. These may include a dimmer, shutter or other enabling function. Check source output, master and blackout settings too. Do not send maximum values to every channel as a shortcut.
- Confirm A Deliberate Change: Make one suitable adjustment and watch the intended fixture respond. For example, use a controlled dimmer change where the fixture provides that function. A power light or data indicator alone does not demonstrate that the command reached the intended function. This check still does not test every feature.
- Extend And Recheck: Following the safe connection procedure, add the next link from the first fixture’s OUT or THRU to the next IN. Keep termination at the new physical endpoint, removing or disabling the previous endpoint termination as its manual directs. Confirm the new fixture’s intended response, then recheck the one already tested.
If an addition introduces a problem, stop extending the line. Note what changed and retain the last proven arrangement as your reference. The timing of the symptom helps narrow the next check; it does not prove the new cable or fixture is defective.
Make any reconnection in a controlled test, not by pulling data during a live show. Loss of DMX does not guarantee blackout; the fixture’s configured behavior matters. Once the route responds as intended, check its addresses separately from its physical order.
Cable order does not set DMX addresses
You do not need to connect the lowest-addressed fixture first. Each light reads its configured channels from the data stream; its position along the cable does not assign those channels. Choose a practical physical route, then check the patch against the settings on each fixture.
Consider a fictional line running from the controller to A, then B, then C. For this example only, assume that each fixture uses eight consecutive channels. These are invented settings, not a specification for any SHEHDS model.
| Physical position | Assumed mode | Start address | Occupied channels |
|---|---|---|---|
| A, first along the cable | Eight channels | 17 | 17–24 |
| B, second along the cable | Eight channels | 1 | 1–8 |
| C, last along the cable | Eight channels | 9 | 9–16 |
The route visits address 17 before address 1, but the ranges do not overlap. Moving B ahead of A would not, by itself, require new addresses. If B performs the wrong function, moving its cable position is therefore a poor first response. Compare its selected mode and start address with the controller’s profile instead.
The distinction also matters when changing a show. Suppose you keep the same positions but select a different mode on B. Its channel footprint—the range it occupies—may change, so review the patch and reserved ranges before reusing the old address list.
When checking dmx stage lighting, use each intended fixture’s exact mode chart for that comparison. A collection label does not establish matching channel functions.
Shared addresses can be deliberate when compatible functions and modes should respond together. They are not a shortcut for making unrelated models mirror each other. Record that intention clearly so another operator does not “correct” a purposeful group. Finally, remember that the highest address does not identify the line’s endpoint: in this example, C still comes last.
Terminate the endpoint and split branches correctly
Follow the cable to find the termination point. In the example above, that is C, even though A has the highest start address. Termination helps control signal reflections at the end of a line; it is not a setting that assigns a fixture’s place in the show.
Use the appropriate terminating plug or the last device’s documented internal termination. Do not combine both. ENTTEC’s termination guidance explains this endpoint distinction and the need to terminate separate splitter output lines.
This gives you a useful way to review a changed layout. If you remove the last fixture, identify where the route now ends rather than leaving the termination plan attached to the old fixture name. If you extend the route, check the new endpoint and the former endpoint’s settings. Mark the endpoint on your route record so the next person can follow the same reasoning.
For two separate routes, use suitable active DMX distribution, not a passive Y cable. ETC’s topology guidance distinguishes a serial line from branches made through a splitter.
Imagine one splitter output feeding stage-left fixtures and another feeding stage-right fixtures. Each output begins its own serial line, and each line has its own last receiver and termination point. Label those endpoints separately; one terminator on stage right does not finish the stage-left route.
Those outputs copy the same input data. They do not create extra independently addressed channel space, so your address plan still matters across the branches. Check the splitter’s own instructions for its input, THRU connection and termination arrangement. Do not assume every active splitter provides electrical isolation.
Adding terminators does not make a passive Y into proper distribution, nor does it explain every flicker. Once the route is correctly arranged, use the scope of any remaining fault to choose a controlled test.
Find the fault by testing one change at a time
First describe the failure without naming a culprit. “B and C stopped responding after the last addition” is a useful observation. “B has a broken output” is a diagnosis that still needs evidence. Keep the test command consistent so you can compare results.
Use the affected group to choose your first check:
| Observed scope | First controlled check | What the result establishes |
|---|---|---|
| The whole line is unresponsive. | Check enabled source output, master and blackout, then test one correctly configured fixture through a known-good short cable. | A response gives you a reference path. No response still leaves source settings, fixture configuration and power to check. |
| A downstream group is affected. | Inspect the route around the first affected position, then compare a suspect fixture on a known-good direct path. | A successful direct test narrows attention to the removed route; it does not identify one failed cable or port. |
| One fixture performs the wrong function. | Compare its profile, mode and address with the exact chart before changing the route. | A corrected response supports a settings mismatch as the cause of that behavior, not a verdict on every other function. |
| Behavior is intermittent. | Review the endpoint and cable condition, then make one controlled substitution while keeping the settings unchanged. | Improvement identifies a useful difference to investigate. Flicker alone does not prove missing termination or a broken cable. |
ENTTEC’s troubleshooting guidance supports checking settings and using bypass tests. The value of the comparison depends on knowing what you removed and what you left unchanged.
Return to the fictional A–B–C route. Suppose B and C fail after an addition while A still responds. In a safe test, try B directly from the verified source through the reference cable, retaining B’s intended mode, address and test command. If it responds, do not immediately order a replacement for the A-to-B cable. The direct path also bypassed A’s through connection and other parts of the original route.
Restore one connection at a time and record where the response changes. If you swap a cable and change B’s mode together, a successful result cannot tell you which change mattered. If B fails even on the direct path, revisit its settings and operating power before treating that result as proof of hardware failure.
Do not perform these interruptions during a live show or assume data loss makes the rig dark. Use the exact equipment procedures and responsible operator control. For an unresolved problem, pass on the tested arrangement, the command used and the observed result. That is a stronger service report than a list of parts you suspect.
Verify the complete line and leave a useful record
After correcting a fault, reassemble the intended route and check it as a whole. Confirm that commands reach the expected physical fixtures, including any deliberate shared-address group. A light that responded alone has not yet demonstrated its intended response within the finished chain.
Keep a concise record that someone else can follow. For the earlier hypothetical setup, an entry might read: “Source to A to B to C; eight-channel modes; addresses 17, 1, 9; C is the terminated endpoint.” Add the actual termination method, branch labels if present, and the change that resolved a problem. Record what you observed, not merely “DMX fixed.”
If interruption and recovery behavior matter to the show, the responsible operator should decide how to check them using the exact manuals and configured settings. For example, the Intimidator Spot 160 ILS Rev3 manual lists Hold, Black, Auto and Sound choices for DMX loss. Those options show why blackout cannot be assumed; they do not establish another fixture’s behavior or the correct choice for your venue.
Finish with the working route, patch details and relevant observations together. The next operator should be able to identify each endpoint and repeat a meaningful check without reconstructing your reasoning from memory.
