DMX512 has been the standard language of fountain lighting for decades, and it works well until a project grows. A plaza fountain with a few hundred fixtures, valve banks spread across several equipment rooms, and a show that must stay in perfect sync begins to expose the limits of a protocol designed around a single cable carrying 512 channels. Designers then meet two unfamiliar names, Art-Net and sACN, usually in a drawing note that says "DMX over Ethernet" with no further explanation. This guide explains what these protocols are, why large fountains use them, how they differ, and how to plan the network and universe count so the system scales without compromising reliability or safety.

What Are Art-Net and sACN and How Do They Extend DMX512?

Both protocols carry standard DMX512 data inside network packets, so the lighting fixtures and valve drivers at the end of the line still speak ordinary DMX. A show controller sends packets over Ethernet to network nodes (gateways), each node converting data into physical DMX outputs placed close to the equipment. Instead of one long daisy-chain cable, a fountain gets a managed network capable of addressing thousands of universes.

To learn more about professional programming, read our DMX512 show control design guide.

Why Do Large Fountains Need DMX Over Ethernet?

Native DMX has hard limits: one universe carries 512 channels, one segment is limited to 32 unit loads, and long cable runs are susceptible to interference. Ethernet removes these constraints. Distributed nodes on a managed network are now the standard approach for large installations, with native DMX reserved for small local clusters.

For the highest level of coordination, ensure your lighting fixtures are fully compatible with your network infrastructure.

Which Is Better for Fountains: Art-Net or sACN?

Both are mature protocols. Art-Net has the widest installed base and supports almost all show controllers. sACN (ANSI E1.31) uses multicast, which is efficient for larger networks, and includes a per-source priority value that supports automatic failover between a primary and backup controller. Pick one protocol for the show network and document it clearly to avoid configuration confusion.

Network Design Best Practices

A fountain control network should be dedicated infrastructure — never share it with general building IT. Use managed gigabit switches, fixed IP addresses, and keep traffic isolated. Nodes should sit in dry, ventilated rooms, while only short, shielded DMX cable runs should reach the water features themselves.

Frequently Asked Questions

Q: What is the difference between Art-Net and sACN?

A: Both carry DMX512 data over Ethernet. Art-Net is widely supported, while sACN offers native multicast support and failover priority features.

Q: How many universes do these support?

A: Art-Net supports 32,768 universes, and sACN supports 63,999, far exceeding the single 512-channel limit of native DMX.

Q: Can I mix protocols?

A: You can, but it is best practice to standardize on one protocol across the show network to prevent configuration complexity and potential sync issues.

Q: Do I need managed switches?

A: Yes, managed switches are recommended to support IGMP snooping (for sACN) and traffic isolation from the main building network.

Conclusion

Art-Net and sACN scale DMX fountain control beyond physical cable limitations by leveraging managed Ethernet networks. Success requires a dedicated control network, careful universe planning, and redundancy that respects the boundary between show control and system safety. Request a Technical Consultation →

© 2026 HUIQI Fountain. All rights reserved. | huiqifountain.com