An Art-Net to DMX converter (usually called a node or gateway) takes lighting data arriving over an ordinary Ethernet network and turns it back into standard DMX512 on a 5-pin or 3-pin XLR socket. It is the bridge between software or a console speaking Art-Net and fixtures that only understand a DMX cable. This guide covers how to choose one and a first-time walkthrough: IP addressing, universe mapping, unicast versus broadcast, testing, and the mistakes behind almost every "no output" support ticket.
What a converter node actually does
DMX512 is a one-way serial signal on dedicated cable: at standard DMX512 speed, one physical cable equals one universe of 512 channels (some nodes, such as the DIN Ethergate MK2, add a faster Overdrive mode that carries multiple universes per port, but only for fixtures built to accept it). Art-Net wraps that same channel data into UDP packets on port 6454, so any number of universes can travel over standard Ethernet. The node sits at the boundary between the two worlds:
- Receive: it listens on the network for ArtDmx packets addressed to the universes it has been configured for.
- Convert: it unpacks each packet into a DMX512 frame with correct timing.
- Transmit: it retransmits that frame continuously on the physical DMX port. DMX receivers expect a constantly refreshed signal, so the node keeps repeating the last received frame between packets. A full 512-channel frame refreshes at roughly 44 times per second regardless of how fast packets arrive (that is the DMX frame rate on the wire, distinct from a fixture's much higher internal PWM dimming rate).
Your fixtures never know a network was involved. If you are new to the protocol itself, read the Art-Net explainer first; this article stays practical.
It works in both directions
Searches for "DMX to Art-Net converter" and "Art-Net to DMX converter" usually land on the same hardware. Quality nodes are bidirectional: each port can be set as a DMX output (network in, DMX out, the common case) or a DMX input (DMX in, network out). The input direction gets a physical console or wall panel onto the network, for example to feed a media server or record into a show controller. Not every node works both ways, though: of the ENTTEC nodes below, the ODE MK3 and DIN Ethergate MK2 support both directions on every port, while the Storm 10's published specifications list DMX output ports only. If you need the input direction, check the datasheet first.
Choosing a node: ports, power, RDM
The differences between nodes are practical:
| Factor | What to check |
|---|---|
| Port count / universes | Each DMX port carries one universe (512 channels) at standard DMX512 speed; some nodes, such as the DIN Ethergate MK2, add a faster Overdrive mode with multiple universes per port, for compatible fixtures only. Count your universes, then add headroom. |
| Power | PoE (IEEE 802.3af) lets one Ethernet cable carry data and power, useful for ceiling and truss mounts. Check for a DC input if your switch is not PoE-capable. |
| RDM support | RDM (ANSI E1.20) lets you readdress and monitor fixtures through the DMX line; over the network it travels as ArtRDM. Not every node or controller implements it, so confirm support on both ends. See the RDM basics article. |
| Connectors and form factor | Stage use favours XLR5 and truss-mountable boxes; installations favour screw terminals and DIN-rail mounting inside an enclosure. |
| Protocol support | Most current nodes speak both Art-Net and sACN. If you have not committed to a protocol yet, see Art-Net vs sACN: which should you use. |
Two ENTTEC examples that cover the common cases: the ODE MK3 (2 bidirectional universes on XLR5, PoE or 12-24 V DC, ANSI E1.20 RDM) suits portable and stage work, while the DIN Ethergate MK2 (2 bidirectional universes on screw terminals, PoE or DC, DIN-rail housing) is built for permanent installations. When the rig outgrows a few universes, the rack-mount Storm 10 handles ten output universes in one box (output only, no DMX-input direction).
Step 1: connect and power everything
For a first test, a direct Ethernet cable from computer to node is fine (no crossover cable needed); for anything bigger, put both on the same switch. Power the node via PoE or its DC supply, and plug a fixture or DMX tester into port 1. Keep this first test small: one node, one fixture, no Wi-Fi (wireless adds its own failure modes, covered in sending Art-Net over Wi-Fi). For real shows, keep lighting traffic on a dedicated switch or VLAN, not the general office or venue network.
Step 2: put the computer and node on the same subnet
This step causes more failures than everything else combined. Art-Net data is plain UDP: if node and sender are not in the same IP subnet, packets never arrive, even though broadcast-based discovery may still find the node. ENTTEC's current nodes (ODE MK3, DIN Ethergate MK2) default to DHCP, falling back to the static address 192.168.0.10 when no DHCP server answers, which is exactly what happens on a direct cable to a laptop. A working first-time setup with an ENTTEC node:
- Node: 192.168.0.10, subnet mask 255.255.255.0 (the DHCP-fallback default)
- Computer: 192.168.0.20, subnet mask 255.255.255.0, gateway left blank
The only rules: every device shares the mask, sits in the same range, and has a unique final address. Set the computer's address manually (static): with no router handing out addresses, DHCP leaves the port unconfigured. Allow the node a moment after power-up to fall back to 192.168.0.10. On a routed network, plain DHCP on both sides also works; find the node via your software's discovery or the router's client list. The Art-Net specification traditionally uses the 2.x.x.x range (mask 255.0.0.0), and some third-party nodes still ship with a 2.x default. That scheme is fine too, but mixing schemes (computer on 192.168.0.x, node on 2.x.x.x) never works. Step-by-step instructions: changing your IP address on Windows or on macOS; networking terminology explains what a subnet mask actually does.
To confirm the link, open the node's web configuration page in a browser (here, http://192.168.0.10). If the page loads, the network layer is done.
Step 3: map an Art-Net universe to a DMX port
In the node's configuration page, each DMX port has a protocol (Art-Net or sACN), a direction (output or input), and a universe number. Set port 1 to output and universe 0, then patch your fixtures to that same universe in your lighting software.
Here is where the off-by-one lives. Art-Net's port-address is zero-based: the first universe is 0. Much lighting software, and all of sACN, counts from 1, so "universe 1" in one tool can mean Art-Net universe 0 or 1, and a node listening on universe 1 may sit silent while the software transmits on universe 0. If a port outputs nothing, trying the adjacent universe number is a legitimate first diagnostic. Art-Net also splits its 15-bit address into Net, Sub-Net, and Universe fields; leave Net and Sub-Net at 0 unless you know you need them. Fixture addressing within the universe works exactly as on a cable: see addressing your fixture.
Step 4: choose unicast or broadcast
Your software needs to know where to send packets:
- Broadcast sends every universe to every device on the subnet. It requires zero per-node configuration, but every device on the network must receive and inspect every packet, so it scales poorly.
- Unicast sends each universe only to the IP address of the node that needs it. It scales far better, at the cost of maintaining an IP-to-universe mapping in your software.
Start with broadcast to prove the chain works, then switch to unicast once you know the node's address. Broadcast is acceptable below roughly 10 universes on a dedicated lighting network; beyond that, unicast (or sACN multicast) keeps traffic sane. Bandwidth planning has the numbers behind that.
Step 5: test the output
You need software that transmits Art-Net. ENTTEC's own applications are free downloads, not trials: EMU gives you faders and sound-to-light and outputs Art-Net directly, and ELM does the same for LED pixel mapping. Either works as a test source even if the show will run from something else.
Bring up channel 1 on the universe you mapped to full. Watch the node's port activity LED: most nodes blink or change colour when valid Art-Net for a patched universe arrives. If the LED shows traffic but the fixture is dark, the problem is on the DMX side (fixture address, cable, termination). If the LED shows nothing, the problem is on the network side.
Common failure points
- Wrong subnet. Computer still on 192.168.1.x while the node fell back to 192.168.0.10, or a third-party node sitting on its 2.x.x.x default. Discovery may still work while data does not. Match the computer's IP and mask to the node (Step 2).
- Firewall. Art-Net uses UDP port 6454, and desktop firewalls routinely drop it, especially when the network is classed as Public. Allow the lighting application through, or open UDP 6454; briefly disabling the firewall is a fair way to confirm the diagnosis.
- Universe off-by-one. Zero-based versus one-based numbering, as above. Try universe 0 and universe 1 on either side, and check the combined Net/Sub-Net/Universe value on both ends.
- Two adapters, wrong exit. Laptops with Wi-Fi plus Ethernet often send Art-Net out of the wrong interface. Select the correct adapter in your software's Art-Net settings, or disable Wi-Fi while testing.
- Port direction. On bidirectional hardware, a port set to input will never output.
- Duplicate IPs. Two nodes fresh from the box share the same default address. Connect and readdress them one at a time.
- DMX-side faults. Once the activity LED shows output, remaining problems are usually cabling, addressing, or termination: see DMX signal loss.
If output is still dead or glitching after these, the Art-Net/sACN troubleshooting guide goes deeper, including packet capture and merging conflicts.
Where to go next
Once one universe runs, scaling is repetition: more ports, more universe numbers, unicast entries per node, and a switch with enough PoE budget. For multi-node rigs, read chaining network devices before you buy cable, and revisit the Art-Net explainer for how universe numbers combine past 16 universes.