> For the complete documentation index, see [llms.txt](https://help.depence.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.depence.com/depence-hardware/modules/depence-logic-module/logic-module-items/network-dmx.md).

# Network DMX

## Network DMX Input (ArtNet, sACN, CITP, Sig-Net)

The **Network DMX** tool group of the Logic Module provides four input objects that let Depence receive incoming DMX data from the network and feed it into the DMX buffer:

| Object                | Protocol            | Typical use                                        |
| --------------------- | ------------------- | -------------------------------------------------- |
| **Input DMX ArtNet**  | Art-Net 4           | Receiving DMX from Art-Net nodes/consoles          |
| **Input DMX sACN**    | sACN (E1.31)        | Receiving DMX via sACN/E1.31 (multicast)           |
| **Input DMX CITP**    | CITP/MSEX           | Receiving DMX from visualizer/media server streams |
| **Input DMX Sig-Net** | Sig-Net (encrypted) | Receiving DMX via the encrypted Sig-Net protocol   |

All four objects follow the same basic principle: they receive DMX data for a freely selectable universe range and write it into the shared DMX buffer according to a configurable **merge mode**. This allows external controllers (lighting consoles, media servers, other visualizers) to be brought live into the 3D visualization.

{% hint style="info" %}
These objects are **inputs**. They receive data from the network. For sending DMX out to the network there are separate output objects.
{% endhint %}

***

### Common behavior

#### Universe range

Each object receives a contiguous range of DMX universes. This is defined by two properties:

* **Start by Universe** – the first universe to receive.
* **Universe Count** – the number of universes received starting from the start value.

The currently configured range is shown directly on the Logic Module node, for example:

```
Univ: 1 to 16
```

{% hint style="warning" %}
The counting of the start value differs depending on the protocol. Art-Net starts at **0** by default, while sACN, CITP and Sig-Net start at **1**. When patching, make sure the universe range set here matches the universe numbers of your fixtures.
{% endhint %}

#### Status output

Each object has an output connector **Status**:

* Value **1** as long as data was received for at least one universe of the range in the current frame.
* Value **0** if no data was received.

This can be used, for example, to build a "signal present" indicator or to trigger logic as soon as an external console is sending.

#### DMX Merge Mode

The **DMX merge Mode** determines how the received values are merged with other DMX sources (cues, other network inputs, etc.) in the buffer:

| Mode                                 | Behavior                                                             |
| ------------------------------------ | -------------------------------------------------------------------- |
| **LTP** *(Latest Takes Precedence)*  | The most recently changed value wins. Default setting.               |
| **HTP** *(Highest Takes Precedence)* | The highest value wins.                                              |
| **Overwrite**                        | The network value overrides other sources with the highest priority. |

{% hint style="info" %}
**LTP** is the default setting and the right choice for most use cases. **HTP** is suitable, for example, for merging multiple dimmer sources. **Overwrite** forces the network source to take precedence.
{% endhint %}

#### Enabled

**Enabled** turns reception on or off:

* **Enabled:** The object receives and processes data. For sACN and Sig-Net it additionally joins the corresponding multicast group.
* **Disabled:** Reception is stopped and the associated buffer range is reset. For sACN and Sig-Net the multicast group is left again.

{% hint style="warning" %}
By default **Enabled = False**. The object only receives data after you have enabled it.
{% endhint %}

***

### Input DMX ArtNet

Receives DMX data via **Art-Net 4**.

#### Properties

| Property              | Description                     | Range                 | Default |
| --------------------- | ------------------------------- | --------------------- | ------- |
| **Enabled**           | Enable/disable reception        | On / Off              | Off     |
| **Start by Universe** | First received Art-Net universe | 0 – 32767             | 0       |
| **Universe Count**    | Number of received universes    | 1 – 1024              | 16      |
| **DMX merge Mode**    | Merging in the buffer           | LTP / HTP / Overwrite | LTP     |

{% hint style="info" %}
Art-Net counts universes **0-based**. The first universe is therefore `0` by default.
{% endhint %}

***

### Input DMX sACN

Receives DMX data via **sACN (E1.31)** using multicast.

#### Properties

| Property              | Description                                     | Range                 | Default |
| --------------------- | ----------------------------------------------- | --------------------- | ------- |
| **Enabled**           | Enable/disable reception (incl. multicast join) | On / Off              | Off     |
| **Start by Universe** | First received sACN universe                    | 1 – 32767             | 1       |
| **Universe Count**    | Number of received universes                    | 1 – 1024              | 16      |
| **DMX merge Mode**    | Merging in the buffer                           | LTP / HTP / Overwrite | LTP     |

{% hint style="info" %}
sACN uses **multicast**. When enabling, as well as when changing the start universe or universe count, Depence automatically joins or leaves the corresponding multicast groups. Make sure your network (switches/routers) properly supports multicast and IGMP.
{% endhint %}

***

### Input DMX CITP

Receives DMX data via **CITP/MSEX**, typically from media servers or other visualizers.

#### Properties

| Property              | Description                  | Range                 | Default |
| --------------------- | ---------------------------- | --------------------- | ------- |
| **Enabled**           | Enable/disable reception     | On / Off              | Off     |
| **Start by Universe** | First received universe      | 1 – 255               | 1       |
| **Universe Count**    | Number of received universes | 1 – 255               | 16      |
| **DMX merge Mode**    | Merging in the buffer        | LTP / HTP / Overwrite | LTP     |

{% hint style="info" %}
For CITP, the start universe and universe count are limited to the range **1–255**.
{% endhint %}

***

### Input DMX Sig-Net

Receives DMX data via the encrypted **Sig-Net** protocol using multicast. Unlike the other protocols, a **passphrase** is additionally required here.

#### Properties

| Property              | Description                                     | Range                 | Default   |
| --------------------- | ----------------------------------------------- | --------------------- | --------- |
| **Enabled**           | Enable/disable reception (incl. multicast join) | On / Off              | Off       |
| **Start by Universe** | First received Sig-Net universe                 | 1 – 32767             | 1         |
| **Universe Count**    | Number of received universes                    | 1 – 1024              | 16        |
| **Passphrase**        | Key for decrypting the Sig-Net stream           | Text                  | *(empty)* |
| **DMX merge Mode**    | Merging in the buffer                           | LTP / HTP / Overwrite | LTP       |

{% hint style="warning" %}
The **passphrase** must match the sender's passphrase exactly. If the passphrases do not match, the packets cannot be decrypted and **no** DMX values are received.
{% endhint %}

{% hint style="info" %}
Sig-Net uses **multicast** and is **1-based** (universe 1 corresponds to the first multicast address). When enabling, as well as when changing the start universe or universe count, the multicast join or leave happens automatically. The join is self-healing: if it was not yet possible when loading the project, it is performed automatically as soon as the connection is ready.
{% endhint %}

***

### Step by step: setting up an input

1. Drag the desired object from the **Network DMX** tool group into the Logic Module.
2. Set **Start by Universe** and **Universe Count** to match your patched fixtures.
3. Choose the **DMX merge Mode** (when in doubt, use **LTP**).
4. For **Sig-Net only:** enter the sender's **passphrase**.
5. Set **Enabled** to *On*.
6. Check the **Status** output or the visualization to see whether data is arriving.

{% hint style="success" %}
As soon as valid data is received, the **Status** output shows the value **1** and the received DMX values appear in the 3D visualization.
{% endhint %}

***

### Troubleshooting

* **No data visible:** Check whether **Enabled** is on and whether the configured universe range matches the universe numbers of your fixtures.
* **Wrong universe offset:** Mind the different counting – Art-Net starts at `0`, sACN/CITP/Sig-Net at `1`.
* **sACN/Sig-Net receive nothing:** Make sure multicast/IGMP works in the network and the correct network interface is used.
* **Sig-Net receives nothing:** Verify that the **passphrase** matches the sender's exactly.
* **Values "flicker" or jump:** Check whether multiple sources are driving the same universe, and choose an appropriate **merge mode** (e.g. **Overwrite** so the network source takes precedence).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.depence.com/depence-hardware/modules/depence-logic-module/logic-module-items/network-dmx.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
