DMX Start Address and Patching: Prevent Fixture Overlap

A DMX fixture's start address identifies the first control slot it uses, while its selected mode determines how many slots it occupies. Match the controller's fixture profile to that mode and allocate a nonoverlapping range. Correct network universe delivery cannot repair a fixture patched with the wrong footprint.

Do this work before recording scenes. Otherwise a later mode correction can move color, dimmer or movement parameters and invalidate carefully programmed content.

Calculate the occupied range

ETC's DMX glossary explains that the start address must be set on the fixture and patched in the control system. ETC's fixture-patching instructions describe assigning DMX addresses to fixtures in the console. Together they support treating fixture setup and controller patch as paired configuration tasks.

For a fixture with a documented footprint of N slots, the last occupied address is start plus N minus one. The following allocation is a hypothetical arithmetic example, not a profile for a named fixture.

A standard DMX universe contains 512 slots. Do not place a fixture near the end without confirming that its complete documented footprint fits within the supported patch arrangement.

Match the personality and mode

The same physical fixture can offer several control modes with different slot counts and parameter layouts. Record the selected mode on the fixture and the profile version in the controller. A profile with the right brand name but wrong mode can produce plausible dimming alongside incorrect color or movement.

Identify fine and coarse channels where the fixture documentation uses multi-slot parameters. Do not patch only the visible major controls while ignoring other occupied slots. Reserved slots still affect the footprint defined by the manufacturer.

When intentionally giving two fixtures the same address, document that they should respond together and ensure their modes match. Accidental overlap is different from a deliberate shared-control choice.

Separate universe mapping from fixture address

A gateway output may receive one network universe and emit a local DMX stream. The fixture's start address belongs within that output stream. Keep controller universe, gateway output and fixture address as separate worksheet columns.

If a fixture responds to the wrong controls, first compare its local mode and address with the worksheet. If an entire chain is wrong or silent, inspect gateway patch and physical output. This order avoids changing every fixture address to compensate for one wrong network mapping.

Validate parameters one at a time

Use a controlled test scene and observe one fixture at a time. Verify dimmer, color and any other approved parameters according to the fixture manual. Keep movement or effect tests within the venue's safe commissioning conditions.

Then test neighbouring fixtures to expose overlaps. A fixture that looks correct alone can still steal slots from the next fixture. Record actual behavior and correct the worksheet before storing final scenes.

Acceptance after maintenance

Read back or inspect each fixture's address and mode after replacement. Check the controller profile and restore the intended gateway universe mapping. A replacement shipped in another mode is not a drop-in match even if its model name is identical.

Include location and mode in the patch export. Bare universe and address numbers are difficult to use when replacing a fixture on a ceiling or truss. Mark shared addresses explicitly so staff know which fixtures should respond together. After replacement, verify adjacent fixtures as well as the new one. This exposes a different footprint that otherwise appears correct on its first parameter while overlapping the next device's allocated range.

Archive the final patch with cable and location labels. The lighting protocol comparison supplies network context. Bring the complete patch to a partner discussion when coordinating AV triggers with a dedicated lighting controller; this guide does not imply native DMX fixture programming in every control product.