Skip to content

dmXLAN Glossary

sACN

sACN (Streaming Architecture for Control Networks) is a network protocol used to send DMX lighting data over Ethernet. Unlike Art-Net, sACN primarily uses multicast, which allows data to be efficiently sent to multiple devices that have joined specific multicast-groups using IGMP.

It’s designed for high-performance lighting control in large installations and is standardized by the ANSI E1.31 specification. sACN supports up to 63,999 universes and is widely used in professional lighting systems for its scalability and reliability.

Art-Net

Art-Net is a protocol for sending DMX lighting data over Ethernet. By default, it uses broadcast to send data to all devices on the local network, ensuring that any Art-Net-compatible device can receive the signal without needing to be specifically addressed. While this makes setup easy, it can lead to unnecessary network traffic. For larger or more complex systems, unicast or multicast can be used to improve efficiency and reduce load.

BlackTrax

BlackTrax, developed by Cast-Soft, is a real-time motion tracking system used in live events to follow performers or objects. It uses infrared beacons and cameras to track position and orientation, sending data to lighting, video, and audio systems to enable automated effects like moving lights and projections that respond to live movement.

Broadcast

Broadcast is a type of network communication where data is sent from one device to all devices on the local network. Every device receives the message, regardless of whether it needs it or not.

This method is simple but can be inefficient, especially in larger networks, because it generates unnecessary traffic. Broadcast is commonly used for tasks like device discovery or initial network setup.

Channel

In DMX terminology, a channel is a single control parameter within a DMX universe. Each channel represents one piece of information that can be sent from the controller to a fixture or device. For example, a channel might control the intensity of a light, the color (red, green, blue), the position of a moving head, or any other attribute.

A DMX universe consists of 512 channels, numbered from 1 to 512. Each fixture uses a certain number of channels depending on its complexity. For instance, a simple dimmer might use one channel for brightness, while a moving light could use 16 or more channels for attributes like pan, tilt, color, gobo, and effects.

In short, a channel is the smallest controllable unit in DMX, and by assigning channels correctly, you tell the controller which part of the fixture to control.

DHCP

DHCP (Dynamic Host Configuration Protocol) is the network protocol that automatically and dynamically assigns IP addresses to devices (hosts) on an IP network.

  • A DHCP server needs to be active on a network to be able to hand out addresses
  • The IP of a device needs to be set to Dynamic to be able to obtain an IP address from the DHCP server

DMX

DMX stands for Digital Multiplex, and it refers to the DMX512 protocol, which is the industry standard for controlling stage lighting and effects. It was originally developed by the USITT (United States Institute for Theatre Technology) and is widely used in entertainment, architectural, and event lighting systems.

DMX512 is a unidirectional digital communication protocol that sends control signals from a lighting controller (such as a console or software) to multiple devices like dimmers, moving lights, LED fixtures, and special effects units. It uses a serial data stream over RS-485 and can control up to 512 individual channels per universe, where each channel typically represents one parameter such as intensity, color, or position.

The protocol is simple and robust, making it ideal for live events. However, standard DMX does not provide feedback from devices to the controller, which is why extensions like RDM were introduced to enable two-way communication.

Dynamic IP

Dynamic IP addressing does not set a fixed IP address for a device. If a DHCP server is present, an IP address is assigned by the server. If a DHCP server is not present, devices automatically get a self-assigned IP. In both cases, the subnet mask is set automatically.

Fixture Profile

A fixture profile is a digital representation of a lighting fixture’s control parameters used by lighting consoles or software. It defines how the fixture’s DMX channels correspond to its functions, such as intensity, color, pan, tilt, gobo, and effects.

Instead of manually remembering which DMX channel controls which attribute, the fixture profile organizes this information into a structured format. When you patch a fixture in your console, the profile ensures that the correct controls appear on the user interface, making programming intuitive.

Fixture profiles are essential for complex fixtures like moving heads or LED units with multiple attributes. They also include details like default values, ranges, and sometimes macros for special effects.

Forced Boot Mode

Starting a device in Boot Mode might be necessary. E.g., to clear the memory or to repair a firmware error. The basic procedure is the same for all types of devices, whereas the button use varies depending on the device.

To start a device in Forced Boot Mode, press the boot button while providing power to the device. Release the button after 1-2 seconds. The display will now display Boot x.x (forced).

Device Boot button
Devices with a black rotary encoder Press the Rotary encoder while powering on the device.
Beltpack X shaped devices Press the bottom right button whilst powering on the device.
Devices without User interface Press the red button on the bottom of the device while powering on the device.

Memory clear

Clearing the memory of a device is recommended after a firmware update. A memory clear is executed by performing the following steps:

  • Start the device in forced boot mode.
  • Release the button.
  • Press the boot button again for 30 seconds - till the timer hits 0.
  • Release the button.
  • After a couple of seconds, turn the device off and back on to return to the normal operation mode.

Firmware error

If corrupted firmware or failure occurs during a firmware update, the display will report a Firmware Error.

To resolve this, perform the following steps:

GDTF

GDTF stands for General Device Type Format. It is an open standard developed by MA Lighting, Robe, and Vectorworks to create a universal way of describing lighting fixtures for use in lighting consoles, visualizers, and CAD software.

The goal of GDTF is to provide a single, consistent file format that contains all the necessary information about a fixture, including its DMX channel layout, physical attributes, 3D geometry, and even gobo and color data. This eliminates the need for multiple fixture profiles across different platforms and ensures accurate visualization and control.

GDTF files are typically used together with MVR (My Virtual Rig) files, which describe the entire lighting setup for easy exchange between design and control systems.

GPIO

The General Purpose In- and Outputs are used to interface with third-party equipment.

HTP

HTP stands for Highest Takes Precedence, and it’s a rule used in DMX lighting control systems to determine which value should be sent to a fixture when multiple sources are providing DMX data for the same channel.

In an HTP merge, the system compares all incoming values for a given channel and uses the highest one. For example, if one controller sends a value of 100 and another sends 200 for the same dimmer channel, the fixture will output 200 because it’s the highest value. This method is commonly used for intensity control, as it ensures that lights never get dimmer unintentionally when multiple controllers are active.

HTP is different from LTP (Latest Takes Precedence), which is often used for attributes like color or position, where the most recent command should override previous ones.

IP address

All host devices on a network need an address to be able to connect to each other, combined with a netmask that determines the segmentation of the network. An Ip address always consists of two parts, a (sub)net address and a host address. The size of both parts is determined with the netmask.

Address

An IPv4 address is 32 bits in size, resulting in a total of 4.294.967.296 theoretically possible unique addresses. For readability, each 8-bit block is represented by its decimal equivalent - resulting in a XXX.XXX.XXX.XXX form where each block of 8-bits an octet has a value of 0 to 255. Not all addresses are freely available, and only specific address ranges are reserved for multicast and private networks. The highest address of a subnet is always reserved for broadcast transmission.

Example IP addresses
  • 192.168.1.101 - 1100000.10101000.00000001.01100101
  • 10.21.4.124 - 00001010.00010101.00000100.01111100

Netmask

The netmask determines which part of the IP address is the sub(net) address and which part is the host address.

The basic netmasks are:

Netmask Binary netmask
255.0.0.0 11111111.00000000.00000000.00000000
255.255.0.0 11111111.11111111.00000000.00000000
255.255.255.0 11111111.11111111.11111111.00000000

A binary position with a 1 sets that part of the address to the net. A 0 sets that part of the address to the host.

IP subnet examples

The IP/netmask combination ...

  • 192.168.1.101 - 255.255.255.0
  • 192.168.1.201 - 255.255.255.0
  • 192.168.4.102 - 255.255.255.0
  • 10.21.4.124- 255.255.0.0
  • 10.21.5.21 - 255.255.0.0

... will enable the following:

  • 192.168.1.101 and 192.168.1.201 are able to communicate on subnet 192.168.1
  • They can not communicate with 192.168.4.102 - who is on subnet 192.168.4
  • 10.21.4.5 and 10.21.5.21 are able to communicate on subnet 10.21

Note that - in this example - communicate means that the devices are able to send each other IP messages, not engage in actual voice communication.

Gateway

Hosts that are not in the same subnet can be routed to be able to send messages back and forth. When a host can not find the destination host in its subnet, it will send the message to the gateway address that is set. Setting the gateway is not needed when devices are in the same subnet and don't need to send messages outside of their subnet.

LTP

LTP stands for Latest Takes Precedence, and it’s a rule used in DMX lighting control systems to determine which value should be applied when multiple sources send data for the same channel. Unlike HTP , which uses the highest value, LTP simply applies the most recent command received.

This approach is commonly used for attributes such as color, position, or effects, where the latest instruction should override previous ones to ensure smooth transitions and accurate control.

Multicast

Multicast is a method of network communication where data is sent from one device to multiple specific devices at once, rather than to all devices (broadcast) or just one (unicast). It’s efficient because the sender transmits a single stream of data, which is then distributed only to devices that have joined a multicast (IGMP) group.

IGMP

IGMP (Internet Group Management Protocol) is a network protocol that allows devices to join or leave multicast groups. When a device wants to receive multicast traffic, it uses IGMP to inform the network. Routers and switches then use this information to forward multicast data only to devices that have requested it, making communication more efficient and reducing unnecessary traffic.

MVR

MVR stands for My Virtual Rig. It is an open file format designed to exchange complete lighting setups between different types of software and hardware, such as CAD programs, visualizers, and lighting consoles.

An MVR file contains all the essential information about a lighting rig, including fixture positions, truss structures, patching details, and associated GDTF fixture profiles. This allows designers, programmers, and operators to share the same data seamlessly across platforms without having to recreate the setup manually.

MVR works hand-in-hand with GDTF because the GDTF files define the fixtures’ technical details, while the MVR file describes the overall rig and its layout. Together, they enable a standardized workflow from design to visualization to live control.

Network item

A network item is a physical dmXLAN device with a network interface to connect to the local dmXLAN network. Not all dmXLAN devices are necessarily a Network item.

Patch

A patch refers to the process of assigning control channels from a lighting console to the DMX addresses of fixtures or devices in the rig. Essentially, it creates the link between the console’s internal control structure and the physical devices on the network.

For example, if a fixture is set to DMX address 101 and uses 16 channels, you patch it so that console channels 1–16 correspond to DMX addresses 101–116. This allows the console to send the correct data to the correct fixture attributes. Patching can also involve mapping multiple universes, merging inputs, or applying softpatchingsoftpatching to reorganize channel layouts without changing hardware settings.

PoE / Power over Ethernet

Some devices in the dmXLAN system are powered by Power over Ethernet, a system that supplies both IP data and power through a single network cable. The standard used by the dmXLAN system is IEEE 802.3af (supporting both, mode A and mode B). Rack-mounted devices and multi-channel stations have a separate 12V DC input allowing for an optional non-PoE power input that can also serve as a redundant power supply.

PTPv2

Precision Time Protocol version 2 the protocol that is used to synchronizes clocks between devices on a network, defined by IEEE 1588-2008 and amended by IEEE 1588-2019 which is backwards compatible with IEEE 1588-2008. Important to note that it is NOT backwards compatible with PTP(v1) IEEE 1588-2002.

RDM

RDM stands for Remote Device Management, which is an extension of the DMX512 protocol. Unlike standard DMX, which only allows one-way communication from the controller to the fixtures, RDM enables two-way communication. This means that controllers can not only send data to devices but also receive information back from them.

With RDM, you can remotely configure settings such as DMX addresses and operating modes without physically accessing the device. It also allows monitoring of device status, including parameters like temperature, lamp hours, and error conditions. Additionally, RDM supports device discovery, so controllers can identify and list all RDM-capable devices on the network.

In short, RDM makes DMX networks smarter and easier to manage by adding feedback and remote configuration capabilities.

RTTrPL

RTTrPL (Real-Time Tracking Protocol – Lighting) is part of the open-source RTTrP suite, designed to transmit real-time tracking data between systems, especially in live entertainment environments.

RTTrPL specifically focuses on lighting control, allowing systems like BlackTrax to send precise positional and rotational data (3D and 6D) to lighting consoles. This enables automated lighting fixtures to follow performers or objects dynamically and accurately during a show.

Self-assigned IP

When a device network is set to dynamic, but no DHCP server is present on the network, the device will receive a self-assigned link-local address. This is a randomly generated address in the 169.254.0.0/16 range with a netmask of 255.255.0.0. Green-GO devices will retain their self-assigned address as long as no other device is using it.

ShowNet

ShowNet, developed by Strand Lighting, is a protocol for sending DMX lighting data over Ethernet. It allows lighting consoles, nodes, and other devices to communicate using standard TCP/IP infrastructure.

Softpatch

A softpatch in lighting control refers to the process of virtually mapping DMX channels from a controller to different fixture addresses without physically changing the wiring or the fixture’s DMX address. It’s essentially a software-based reassignment that allows you to organize and control your rig more efficiently.

For example, if a fixture is set to DMX address 101 but you want it to respond to channel 1 on your lighting console, you can create a softpatch that links console channel 1 to DMX address 101. This is extremely useful for reorganizing channel layouts, grouping fixtures logically, or adapting to changes in the rig without touching the hardware.

Static IP

When a static IP address is used, devices (hosts in the network) are manually given their own unique IP addresses. Special care must be taken to ensure that all devices are in the same subnet.

The default setting for a dmXLAN device is a static IP address within the 2.x.x.x range (Art-Net). In practice, this means that other Art-Net devices on the local network can communicate with dmXLAN devices without additional configuration.

Unicast

Unicast is a type of network communication where data is sent from one device directly to one specific device. It’s a one-to-one transmission, meaning only the intended recipient receives the data.

This is the most common form of communication on networks, used for things like web browsing, emails, and file transfers. Unlike multicast or broadcast, unicast is more private and controlled, but can be less efficient when the same data needs to be sent to multiple devices.

Vision.Net

Vision.Net is a fully integrated architectural lighting control system developed by Vari-Lite. It’s designed to manage lighting across a wide range of environments—from single rooms to large multi-building campuses.

VLAN

A VLAN - or Virtual Local Area Network - is a way to divide a physical network into smaller, isolated virtual networks. Devices in the same VLAN can communicate with each other, even if they’re connected to different switches. Devices in different VLANs are kept separate unless routing is configured between them. VLANs improve network organization, security, and traffic management.