DALI or DMX512? Use Cases and How to Choose
Both are lighting control protocols, both digital, both decades old in the field. But they were designed to solve different problems, and substituting one for the other is expensive and frustrating. The short answer: movement and effects mean DMX512; buildings and maintenance mean DALI.
In short
- DMX512 is for performance: fast, one-way, 512 channels per universe.
- DALI is for facilities: slow but bidirectional, 64 addressable luminaires per line.
- In DALI the intelligence lives in the luminaire (groups and scenes stored on the device).
- If you need fault or energy reporting, DMX alone will not do it.
- DMX wiring is rule-sensitive; DALI wiring is electrician friendly.
- Both can coexist in one building — use a gateway to trigger scenes, not to stream.
The distinction in one sentence
DMX512 was designed for performance: one operator, rapidly changing looks, dozens of updates per second. DALI was designed for facilities: hundreds of luminaires, levels that rarely change, but a need to know the state of every one.
That single design choice produces every difference below.
Side by side
| DMX512 | DALI | |
|---|---|---|
| Standard | ANSI E1.11 | IEC 62386 |
| Direction | One-way (bidirectional with RDM) | Bidirectional |
| Data rate | 250,000 bit/s | 1,200 bit/s |
| Refresh | ~44 times per second | Command based, no continuous stream |
| Capacity | 512 channels per universe | 64 addresses per line |
| Addressing | Start address + channel count | Unique address per device |
| Grouping | Virtual, in the console | Real, in the device (16 groups, multiple membership) |
| Scenes | Stored in the console | In the luminaire’s memory (16 scenes) |
| Feedback | None (except RDM) | Yes: level, fault, hours, energy |
| Topology | Daisy chain only | Free (except ring) |
| Terminator | Mandatory (120 Ω) | Not needed |
| Cable | 120 Ω shielded twisted pair | Two cores, mains-rated |
| Polarity | Matters | Does not matter |
| Distance | ~300 m per segment | ~300 m per line |
| Installation difficulty | Rule-sensitive | Electrician friendly |
What the differences mean in practice
1. Speed: can you do effects?
DMX refreshes the whole universe roughly 44 times a second. A moving head’s smooth sweep, a strobe hit or a fast chase are only possible at that rate.
DALI runs at 1200 bit/s and sends no continuous stream; it is command based. You tell a group “go to 30% over four seconds” and the luminaires do it themselves. That is ideal for a building — bus traffic is almost nil — and useless for stage effects.
2. Feedback: how do you learn about a fault?
With DMX you do not. The console sends and hopes; if a fixture is dark, someone has to look. On stage that is fine, because everyone is already looking at the lights.
In a car park with 800 luminaires it is a real operational problem. DALI polls each device and reports the faulty one. For emergency lighting the system performs and logs the periodic tests regulation demands. On many projects that alone decides the protocol.
3. Where the intelligence lives
In DMX all intelligence sits in the console; the fixture just applies the number it receives. If the console dies, the system stops.
In DALI intelligence is distributed: each luminaire holds its own group memberships, 16 scene levels, fade curve and failure behaviour in its own memory. The controller only says “scene 3”. Even with the controller down, a wall switch can keep working.
4. Wiring: who are you hiring?
DMX wiring is rule-sensitive: correct impedance, daisy chain, terminator, 32 devices per segment. Someone unaware of these builds a system that appears to work but is unstable.
A DALI line can be pulled by an ordinary electrician with familiar two-core cable in whatever topology suits the building. On a construction project that is a significant planning and cost difference.
Which protocol for which project?
| Application | Choice | Why |
|---|---|---|
| Concert, theatre, stage | DMX512 | Speed, effects, moving heads |
| Nightclub, live performance | DMX512 | Colour, chases, strobes |
| TV and film studio | DMX512 | Fast relighting, colour control |
| Office, school, hospital | DALI | Addressing, daylight harvesting, fault reporting |
| Hotel rooms and corridors | DALI | Scenes, silent dimming, maintenance |
| Car park, warehouse | DALI | Sensor integration, energy and fault reports |
| Emergency lighting | DALI | Automated testing and reporting |
| Retail display (dynamic) | Depends | Static scenes DALI; moving accents DMX |
| Facade lighting | DMX512 | Colour transitions, animation, pixel control |
| Museum / gallery | DALI | Precise static levels, lifetime tracking |
| Restaurant, bar | DALI | Time-of-day scenes, low maintenance |
| Theme park show | DMX512 | Synchronised effects and timing |
Running both: gateways
Most real projects contain both. A hotel lobby runs architectural lighting on DALI while the ballroom stage rig runs DMX. Two systems in one building is entirely normal.
If you want to link them, DMX-to-DALI gateways exist. Use them knowing the limits:
- Passing commands from DMX to DALI works, but DALI’s response cannot keep up with DMX’s refresh rate. Smooth fades pass through; fast chases do not.
- DALI’s feedback cannot be carried back into DMX — there is no such channel. Fault reports must still be read on the DALI side.
- Address mapping is done by hand and will be lost at the first maintenance visit unless documented.
- Rule of thumb: use the gateway to trigger (“when DMX channel 12 rises, recall DALI scene 4”), not for continuous channel-by-channel control.
The cost side
DALI drivers usually cost more per luminaire, and commissioning is a separate line item. In return it pays back over time: labour spent hunting faults, emergency lighting testing and energy savings close the gap within a few years.
On the DMX side hardware is cheap, but doing it properly takes knowledge: decent cable, opto-isolated splitters, terminators. Cutting those corners returns later as hours of troubleshooting.
Five questions to decide
- Do the lights need to change more than once per second? → If yes, DMX512.
- Do you need to know which individual luminaire has failed? → If yes, DALI.
- Who will operate the system — a lighting operator or a facilities manager?
- How many luminaires and how many scenarios? Over 64 devices means extra DALI lines; over 512 channels means extra DMX universes.
- Who is pulling the cable — the stage crew or the building electrician?
The answers almost always point one way. If they do not, the project probably genuinely needs both systems — and that is perfectly normal.
Related articles
Project and product support
Stuck somewhere in your installation, or unsure which product fits? Drop us a line for project consultancy and product support.
