DMX over Ethernet: Art-Net and sACN in Practice
For larger or multi-universe lighting installations, DMX512 universes move onto Ethernet/IP using Art-Net or sACN -- here's what that means for your network design and cabling, honestly explained.
How DMX-over-Ethernet works on site
Console outputs Art-Net or sACN
The lighting console (or media server) packages DMX universes as Art-Net or sACN/E1.31 packets and sends them out over Ethernet instead of a direct RS-485 line.
A managed network segment carries it
A dedicated or clearly managed network segment carries the lighting traffic, reducing collisions with other IT traffic on larger sites.
Nodes convert back to DMX512
Node/gateway devices positioned near the fixtures receive the Ethernet packets and convert them back to DMX512 RS-485 output.
DMX512 wiring takes the last run
From each node, standard DMX512 daisy-chain wiring -- with its 120-ohm terminator and unit-load limits -- carries the signal to the fixtures.
What matters in an Ethernet-based DMX network
sACN carries the official standard
sACN is the ANSI/ESTA-standardised protocol (E1.31) with native multicast support -- Art-Net remains the de-facto industry default, not an official standard.
Multi-universe scale
Ethernet/IP infrastructure lets you carry and manage many DMX universes on shared cabling, instead of one universe per RS-485 run.
Two protocols, two profiles
Art-Net is the de-facto protocol from Artistic Licence, extremely widely adopted; sACN/E1.31 is the official ANSI/ESTA standard with multicast.
Choice driven by your gear
Which protocol you use is usually dictated by what your console and fixture nodes actually support -- check compatibility before committing.
Segmented network discipline
Lighting traffic on its own dedicated or managed segment avoids collisions with general IT traffic, especially as universe counts grow.
DMX512 is still the last mile
Nodes convert Ethernet back to RS-485 near the fixtures -- daisy-chain topology, termination and unit-load limits still apply at that stage.
What we help with
Network-practice support for integrators bringing DMX onto Ethernet
- Network segment and topology review for lighting traffic
- Art-Net vs sACN protocol guidance based on your console and fixtures
- Node/gateway placement and panel integration
- DMX512 physical-layer verification: daisy-chain, termination, unit-load budget
- As-built documentation and handover
Frequently asked questions
Is Art-Net an official standard?
No. Art-Net is a de-facto protocol from Artistic Licence -- extremely widely adopted across the lighting industry, but it is not an official ANSI or ESTA standard. sACN (E1.31) is the official ANSI/ESTA standard alternative.
Should I choose Art-Net or sACN?
It's often decided by what your console and nodes already support. sACN's native multicast is efficient when several nodes need the same universe, but always confirm compatibility on both ends before specifying.
Do I still need DMX512 cabling once I'm on Ethernet?
Yes. Nodes/gateways convert the Ethernet packets back to DMX512 RS-485 for the final run to fixtures, so daisy-chain topology, the 120-ohm terminator, and unit-load limits still apply at that stage.
Is DMX512 the same as DALI?
No, they're different protocols for different jobs. DMX512 is built for dynamic, scene-based, fast-changing lighting control; DALI is for standard building-lighting ballast/driver control such as dimming, not scene-based show control.
Should lighting traffic share our regular IT network?
On larger installations we recommend a dedicated or clearly managed network segment for lighting traffic, to reduce collisions and interference with everyday IT traffic.
Planning a multi-universe installation?
Talk to our engineers about network topology, protocol choice and node placement before you commit to hardware.