DMX is the one piece of stage technology that almost every lighting problem eventually leads back to. A fixture that will not respond, a colour that will not change, a rig that behaves differently in a different venue — the cause is usually a patch decision, not a faulty light. This guide covers what DMX actually is, how addresses and universes work, and the patch choices that prevent most on-site surprises.
In this guide
DMX512 is a one-way serial control protocol. A controller broadcasts a continuous stream of “channel levels” — 512 values, each from 0 to 255 — roughly 44 times per second. Every fixture on the line receives the entire stream; each fixture reads only the channels it has been told to watch.
Three properties follow from that design, and they explain almost every DMX behaviour that confuses people.
| Property | Consequence in practice |
|---|---|
| One-way | Fixtures never report back. The desk cannot know a fixture is unplugged, misaddressed or broken. Diagnostics are visual. |
| Broadcast | Every fixture sees every channel. Two fixtures with the same address will always behave identically — this is the classic patching bug. |
| Refresh, not commands | Levels are resent continuously. A fixture holds its last received look, which is why pull the data and everything freezes rather than going dark. |
| 512 per line | Capacity is finite and shared. Consuming channels with high-resolution modes has a real cost. |
There is no handshake, no acknowledgement, no device discovery. Whatever the desk sends is what the fixtures act on. Every “the fixture ignores me” problem is either wrong address, wrong mode, or a data path that never delivered the stream.
A universe is one DMX line: 512 channels of level information, all sent together. The number sounds generous until you count what modern fixtures consume.
Here is what the same style of product costs in channels across its switchable modes, using published profiles from this site’s own fixtures as the example:
| Fixture | Simple mode | Full mode | Universe usage at full mode |
|---|---|---|---|
| HUEWAVE RGBW 200 COB IP | 4 CH | 10 CH | 1.9% of a universe |
| LIMONA PAR 2415IP | 6 CH | 10 CH | 1.9% |
| HUEWAVE 19Z PAR | 10 CH | 18 CH | 3.5% |
| HUEWAVE Moving Head 1915Z | 16 CH | 24 CH | 4.7% |
| HUEWAVE PIXEL BAR 1810R | 12 CH | 110 CH | 21.5% — 4 bars fill a universe |
| PULSARIS BAR 720B | 4 CH | 168 CH | 32.8% — 3 bars fill a universe |
The pattern is the whole lesson: a wash par is a rounding error, and a pixel-mapped bar is a major consumption of your only line. Sixteen dual-tone wash fixtures can share a universe comfortably. Six pixel bars cannot.
Per-LED and per-section control looks free in the product page and is not free on the data line. A bar advertised as “168 CH” consumes a third of a universe in full mode. Two or three of them, and you are adding a second universe and the hardware that carries it.
Most controllers offer only one universe. Moving beyond it means either a second output from a larger desk or a protocol that carries multiple universes over one cable — Art-Net or sACN running over Ethernet. That upgrade is a data distribution decision, not a lighting design decision, and it is far cheaper to plan before load-in than to solve in a venue basement.
Each fixture is assigned a DMX start address. That address is the first channel the fixture listens to. It then listens to the next N channels in sequence, where N is the number of channels its current mode uses.
If a fixture in 24-channel mode starts at address 1, it occupies channels 1 through 24. The next fixture in that mode must start at address 25 — not 2, and not 24.
Overlapping addresses are the single most common cause of “this fixture copies that fixture”. Two fixtures listening to the same channels will always do the same thing, because that is exactly what a shared address means.
A patch is the map between desk faders and fixture channels. Most modern desks let you patch a fixture by profile — you tell the desk the model and the mode, give it a start address, and the desk works out the channel layout. Two decisions are still yours.
DMX runs electrically as RS-485: a differential pair on 120 Ω cable, with a specified topology. Departing from that specification produces intermittent faults that are hard to reproduce and easy to blame on fixtures.
| Rule | Why it exists | Symptom when broken |
|---|---|---|
| 120 Ω DMX cable, not microphone cable | Mic cable has the wrong impedance and no data pair | Random flickering, fixtures responding late, works then stops |
| Maximum 32 devices per daisy chain | Electrical load on the driver | Fixtures at the far end behave erratically or not at all |
| Daisy chain, not a star | RS-485 expects one continuous line | Reflections cause data corruption on part of the run |
| Terminator on the last fixture | Absorbs reflections at the end of the line | Intermittent faults that appear only on longer runs |
| Keep data away from mains runs | Induced noise on an unshielded or long parallel run | Dropouts that correlate with other equipment switching |
Three-pin XLR is widely used at the budget end and five-pin XLR is the professional convention, but the data on them is identical DMX512. The practical difference is mechanical: five-pin connectors are more rugged and less likely to be confused with an audio line. Adaptor cables work, and are also the most commonly misplaced item in any lighting case.
The 32-device rule is why an optically isolated splitter is one of the most useful pieces of hardware in a rig. A DMX splitter takes one input and drives several isolated outputs, so the rig is wired as a star from a central point rather than one long chain that all 40 fixtures depend on.
The two benefits are capacity and fault isolation. Capacity, because each output branch carries its own share of the device count. Fault isolation, because a damaged cable on one branch no longer takes the whole rig down — and because outputs are optically isolated, a ground potential difference between two parts of a building cannot travel down the data line as hum.
DMX SPLITTER
$110
HEMERA DMX C384
$99
If the rig will exceed roughly 20 fixtures on one line, if the data run crosses between buildings or between separate electrical supplies, or if the truss is wired in a physical star anyway, use a splitter. It costs less than the labour of diagnosing a ground loop on site.
Wireless DMX has earned a permanent place in rigs, and it is not a drop-in replacement for cable. The honest comparison:
Console choice follows from universe count and programming time, and not from brand loyalty. The three realistic starting points for a small to mid-size rig:
One universe, hands-on
Growing past one universe
Software plus a node
Hardware only, no computer
Notice that the pixel-mapping capability drives the console decision. If the rig has no pixel fixtures, one universe is enough and a hands-on desk is the cheapest reliable answer. If the rig has pixel bars, the requirement jumps to multi-universe networking — a completely different hardware category.
Use 120 Ω DMX cable rather than microphone cable, stay inside 32 devices per chain, and terminate the last fixture on every branch. Most intermittent “dead fixture” calls are resolved by those three, in that order.
512 channels. They are sent continuously, roughly 44 times per second, on a single data line. Every fixture on that line listens to the same stream and reads only the channels within its own footprint, which is why channel budgeting matters as soon as a rig includes pixel or multi-emitter products.
They can, and they will then behave identically in every respect — same intensity, same colour, same movement. This is occasionally deliberate, when two fixtures in different positions are meant to mirror each other. It is far more often the cause of a bug. If a fixture appears to be copying another, address overlap is the first thing to check.
Intermittent DMX faults almost always trace to the data path rather than the fixture. Check in this order: microphone cable used for data instead of 120 Ω DMX cable, more than 32 devices in one daisy chain, a missing terminator at the end of the run, a data cable run parallel to mains power, or a damaged connector. Faults that appear only on long runs point at termination or cable quality.
Nothing electrically — it is the same DMX512 data either way. Five-pin XLR is the professional convention and is more robust; three-pin XLR is common on lower-cost fixtures and is more easily confused with an audio connection. Adaptor cables between the two work correctly, and are worth carrying in quantity.
The DMX512 specification allows 32 devices per daisy chain, and that limit is electrical rather than about channel capacity. If the rig is physically arranged in a star, or exceeds the device count, use an optically isolated splitter. Splitting also improves fault isolation, so one damaged cable no longer takes down the entire rig.
No. Below roughly 20 fixtures on one continuous chain, a splitter adds cost and complexity without solving a problem you have. It becomes worthwhile when the device count approaches the limit, when the data run crosses between separate electrical supplies, or when the cabling is physically a star and would otherwise require a long unnecessary loop.
This article describes general DMX512 practice and the published specifications of products sold on sanyilights.us at the time of writing. Channel counts, modes and features vary by fixture model and firmware version — always confirm the current datasheet before patching a production. Electrical and data installation must comply with local codes and the manufacturer’s instructions. Product availability and pricing are subject to change.
