Lighting and control

Network control: Art-Net, sACN and nodes

Document the path from console to DMX output and fixture.

Ask GLMedia about a lighting rental solution for your event, subject to availability and technical requirements.

Using this guide

Art-Net and sACN carry lighting data over a network. A node converts or routes according to its functions and settings; connecting it does not create a correct patch.

Prepare your rental inquiry

Date, city, venue and setup, event and pickup schedule.
Intended use, area dimensions and equipment already supplied by the venue or production.
Known console and nodes, areas and approximate universes; sketch the source, network and DMX outputs. Include protocols and versions if available, leaving unknown details open.
Network owner and restrictions, available ports and an authorized test window; say whether you need equipment, signal-route planning or setup to assess.

Specify equipment only or whether setup, programming, operation and strike are also needed. Scope is confirmed in the proposal.

You do not need a final equipment list: tell us the result you want and the part you need help with. Availability and scope are confirmed in the proposal.

Features and connections

Use NET-X II as an example and consult its specific guide. Protocol, input/output port, universe and merging are separate settings.

Before proposing nodes or ports, mark which source must reach each area and where it becomes DMX. Check supported protocol, universe mapping and port direction on the actual devices. For a shared network, agree on testing with its owner; a sketch and known equipment can start the discussion without inventing an IP plan or changing a production network.

Prepare the system

Draw console, network interface, switch, node and DMX branch. Record unique IPs, mask, protocol and universe mapping without blindly changing venue networking.
Test one source, universe and output with a known receiver; confirm the equipment is authorized to transmit data.
Save configuration and prepare recovery; review source-loss behavior at both node and fixture.

Questions and troubleshooting

Is the node visible but no DMX comes out?

Network visibility does not prove useful port data.

Confirm console output interface, protocol and transmitted universe; then verify OUTPUT status and assigned universe.
Test the DMX branch separately with a short cable; Ethernet link does not validate patch.

Are universes shifted?

Compare numbering displayed by both devices.

Record protocol, decimal/hex display and network universe as well as the console’s internal universe.
Do not assume a universal offset; verify mapping with one known output and parameter before replication.

Does another source change levels or prevent blackout?

Check merging, concurrent sources and recovery.

For NET-X II, manual Rev. 8 states that console sACN priority is ignored when merging in HTP or LTP. Verify SINGLE, HTP or LTP for the design; do not apply this rule to other nodes.
Safely test loss and return of each source. Hold, Blackout and Stop DMX do not guarantee identical final behavior at every fixture.

Precautions

Do not connect DMX on a network-style connector to Ethernet without manufacturer identification.
Do not change VLAN, multicast, firewall or shared networking without coordinating with the system lead.
Do not update firmware during the show; retain compatible recovery configuration and backup.

Terms on this page

DMX: A data protocol controlling lighting functions; each model defines what its channels mean.
Patch: Assignment of fixture, profile, address and universe in the control system.

Documentation and sources

Accessed: 2026-10-22. Coordination guide and proposed checks; no GLMedia physical testing.

Guides to plan your system

Help us improve this guide

Is an explanation missing, did you find an error, or did you solve something differently? Tell us on WhatsApp.

Ask a question Share how I solved it Suggest a correction

WhatsApp opens with an editable draft. Review it and send it if you choose. Do not include passwords, keys or client information. Contributions are reviewed before being added to guides; they are not published automatically.