This page shows the control scheme of an eDMX (Art-Net or sACN) rig built on ENTTEC hardware: what connects to what, from the software or console generating channel data down to the fixtures on a DMX line. Use it as the map; the linked articles cover each stage in depth.
The signal chain
Every Art-Net or sACN system has the same four-stage shape:
Controller or software → Ethernet network → eDMX node → DMX fixtures
- Controller or software generates the channel data: a lighting console with an Ethernet port, or an application on a computer. ENTTEC's EMU (faders and sound-to-light) and ELM (LED pixel mapping) both transmit Art-Net and are free to download; many third-party packages work too, see compatible software.
- Ethernet network: a standard switch and Cat5e/Cat6 cable. Nothing lighting-specific is required, though a dedicated switch or VLAN for lighting traffic is good practice. Art-Net travels as UDP on port 6454; sACN uses multicast. One universe at a fast refresh rate is roughly 0.3 to 0.4 Mbit/s, so bandwidth is rarely the limit (bandwidth planning has the numbers).
- eDMX node: the converter that receives network packets and regenerates physical DMX512 on its ports. Each DMX port carries one universe of 512 channels at standard DMX512 speed.
- DMX fixtures daisy-chain from the node's port exactly as they would from a console's DMX output. Normal fixture addressing and cabling and termination rules apply on this side of the node.
Which ENTTEC node goes where
| Node | Universes | Built for |
|---|---|---|
| ODE MK3 | 2, bidirectional, XLR5 | Portable and stage use; PoE or 12-24 V DC |
| DIN Ethergate MK2 | 2, bidirectional, screw terminals | Permanent installations, DIN-rail mounting |
| Storm 10 | 10, output only | Rack-mount, larger rigs |
Variations on the scheme
- DMX input to the network. On bidirectional nodes (ODE MK3, DIN Ethergate MK2) a port can run the other way: a physical console or wall panel feeds DMX into the node, which transmits it as Art-Net or sACN, for example into a media server or show recorder. The Storm 10 is output only.
- Multiple sources. Two controllers can send the same universe at once, for example a console plus a backup or a playback device. The node combines them by sACN priority, HTP, or LTP depending on configuration; see output merging.
- Wireless links. Wi-Fi can replace a cable run in small rigs, with real trade-offs covered in sending over WiFi.
- Several nodes. Larger rigs repeat the pattern: one switch, many nodes, each mapped to its own universes. See chaining network devices.
What every link in the chain needs to agree on
- IP addressing. Sender and node must sit in the same subnet with the same netmask. ENTTEC's current nodes default to DHCP and fall back to 192.168.0.10 when no DHCP server answers.
- Universe numbers. The universe set on the node's port must match the one your software transmits. Art-Net counts from 0, much software counts from 1, so an off-by-one is the first thing to check when a port is silent.
- Delivery mode. Broadcast works with zero configuration on small networks; unicast (or sACN multicast) scales better. The reasoning is in Art-Net vs sACN.
To build this chain for the first time, follow the step-by-step converter node setup guide. For how the protocol itself works underneath, read the Art-Net explainer.