DMX Address Overlap: Universe, Start Address and Fixture-Footprint Planning

LikeLight Tom · Operations · Technical reviewer: pending confirmation

Summary

Two DMX fixtures responding together is often called a signal problem, but it may be a patch problem: duplicated start addresses, overlapping footprints, the wrong fixture personality, or a mode change that made a fixture occupy more slots. Termination and cable replacement cannot correct a logical overlap.

A DMX universe can carry up to 512 data slots under ANSI E1.11-2024 [S1]. A fixture's **start address** is its first slot; its **footprint** is the number of consecutive slots required by the selected mode [S2]. The occupied range is:

**end address = start address + footprint − 1**

The range is valid only when it does not overlap another fixture and the end address is no greater than 512.

1. Diagnose the symptom before repatching

ETC's universe view marks base addresses, occupied footprint cells and overlaps [S2]. Keep the same separation in the project records: logical patch, physical DMX line and network routing are different drawings.

2. Universe calculation examples

These examples teach arithmetic; they do not describe the LIKELIGHT wall washer personality.

Consecutive 6-slot example

If fixture 1 starts at address 1 with a 6-slot footprint, it occupies 1–6. Fixture 2 may start at 7 and occupies 7–12. For fixture number *n* in a gapless sequence:

**start(n) = 1 + (n−1)×6**

Fixture 12 starts at 67 and ends at 72. ETC documents a comparable rule: multiple devices consume the number of addresses defined by their footprint and undersized spacing creates overlap [S3].

Boundary example

A 16-slot fixture starting at 497 occupies 497–512 and fits exactly. Starting it at 498 would require 498–513 and is invalid in that universe. Move the entire fixture to the next universe unless the manufacturer's approved personality explicitly supports a split—which should not be assumed.

3. Footprint is defined by mode, not housing

The same luminaire may have a basic mode and an extended mode. Additional dimmer, strobe, macro, calibration or 16-bit parameters can enlarge the footprint. A 16-bit parameter normally consumes coarse and fine slots; do not count parameter names instead of occupied slots.

ETC notes that RDM mode changes can alter footprint and collide with an adjacent device [S4]. Treat every mode change as a patch change: recalculate, update the console personality, relabel the fixture and retest.

4. A practical patch workflow

1. Freeze every fixture model, firmware and operating mode.
2. Obtain the manufacturer-approved personality/channel table; mark unknown items pending confirmation.
3. Calculate start and end address for each fixture, including intentional gaps and reserved slots.
4. Check that every range stays within 1–512 and that no two ranges overlap.
5. Map console universe numbers to physical outputs or Art-Net/sACN universes explicitly.
6. Program and label each fixture with universe, start address, mode and zone.
7. Test every parameter one at a time at safe output levels.
8. Export the console show, fixture personalities and an as-built address schedule.

5. Universe numbering can create a second error

“Universe 1” in one application may map to a different numeric convention or physical port elsewhere. Record a full path: console universe → network protocol universe → node output → physical DMX line → fixture range. Do not rely on a label alone.

Network source ownership is separate from slot allocation. Two transmitters, priorities or merging can change received values even when the fixture ranges are correct. Diagnose source routing and merge policy independently.

6. LIKELIGHT evidence boundary

LIKELIGHT's public page identifies model L-W-10036-DMX as a 36 W, DC24 V, RGB, DMX512 wall washer [S5]. It does not publish the exact personality, footprint, channel order, RDM support or firmware behavior. This article therefore does not assign it an assumed 3-channel RGB mode.

For an inquiry, provide product code, quantity, controller, required functions, preferred mode, universe plan and addressing schedule. Request the approved channel chart and sample verification for the ordered configuration.

7. When not to change DMX addresses

• Do not repatch random flicker that follows cable movement, moisture or termination changes.
• Do not force a smaller footprint than the selected mode actually uses.
• Do not reuse one address intentionally unless mirrored control is documented and accepted.
• Do not split one fixture across universes without explicit manufacturer/controller support.
• Do not change RDM mode without recalculating adjacent ranges.
• Do not approve a patch from the console view alone; verify the physical fixture displays and one-parameter tests.

FAQ

How many RGB fixtures fit in one DMX universe?

In a purely illustrative 3-slot RGB mode, 170 fit with two slots spare. The actual fixture may use more channels.

Can two fixtures share the same start address?

They can mirror the same values, but only when that behavior is intentionally designed, documented and accepted. Otherwise it is an address conflict.

What is fixture footprint?

The number of consecutive DMX slots required by the selected fixture mode [S2].

Why did changing mode break the next fixture?

The new mode may occupy more slots and overlap its neighbor [S4]. Recalculate and repatch.

Can a fixture start at address 512?

Only if its footprint is one slot. Any larger footprint would cross the universe boundary.

Does RDM automatically prevent every overlap?

No. RDM can set modes and addresses, but the control-system patch still requires validation and documentation.

Sources checked

2026-09-10

1. S1: ANSI E1.11-2024 — USITT DMX512-A
2. S2: ETC — DMX Glossary
3. S3: ETC ColorSource — Add Device
4. S4: ETC ColorSource — About RDM
5. S5: LIKELIGHT — 36 W DC24 V RGB DMX wall washer

LIKELIGHT L-W-10036-DMX wall washer example

Submit project requirements