Wiki source code of sACN and Art-Net Receive (eDMX Receiver)
Last modified by Alexander Mott on 2024/06/13 19:47
Show last authors
author | version | line-number | content |
---|---|---|---|
1 | ShowRunnerCLC™ comes standard with a built-in eDMX receiver capable of receiving sACN or Art-Net packets from a third-party DMX controller and mapping those received eDMX values into output levels for ShowRunnerCLC™-controlled hardware. This allows a third-party DMX controller (such as a theatrical control panel) to directly command ShowRunnerCLC™-controlled loads through eDMX. One common use-case for this feature is to allow individuals running a theatrical event to use their temporarily installed DMX console to directly control ShowRunnerCLC™ house lighting as if they were DMX fixtures, without the need to use Crestron keypads or touch screens. | ||
2 | |||
3 | = Hardware Requirements = | ||
4 | |||
5 | These are the hardware/networking requirements for integrating a third-party DMX controller with ShowRunnerCLC™'s eDMX receiver: | ||
6 | |||
7 | * Third-party controller must be capable of sending eDMX commands via sACN or Art-Net | ||
8 | * Third-party controller must be able to send eDMX signals to the lighting control processor (i.e. third-party controller must be on the same LAN or VLAN as the lighting control processor, or the building LAN must be configured in such a way as to allow this communication) | ||
9 | * If either of the above cannot be achieved, then a [[DIN-SACN-DMX (Enttec DIN Ethergate 2)>>https://www.crestron.com/Products/Lighting-Environment/Lighting-Fixture-Accessories/Interfaces/DIN-SACN-DMX]] or similar device must be added to the ShowRunnerCLC™ controlled hardware | ||
10 | ** DIN-SACN-DMX will have traditional DMX connection to the third-party controller and receive ordinary DMX (non-eDMX) signals from the third-party controller | ||
11 | ** DIN-SACN-DMX must be on the lighting control LAN/VLAN | ||
12 | |||
13 | = Information Requirements = | ||
14 | |||
15 | The following information/coordination must be arranged by the Agent prior to the eDMX receiver being added to the ShowRunnerCLC™ configuration: | ||
16 | |||
17 | * **(Required)** eDMX type (sACN or Art-Net) | ||
18 | ** If traditional DMX is used, then sACN from a DIN-SACN-DMX receiver is assumed | ||
19 | * **(Required)** Universe/Channel to ShowRunnerCLC™ load map | ||
20 | ** Agent must coordinate which eDMX channels are used to control each ShowRunnerCLC™ load or load group | ||
21 | ** If traditional DMX is used, Agent must still coordinate which DMX channels should correspond to which ShowRunnerCLC™ load or load group | ||
22 | ** Multiple eDMX receivers can be defined in ShowRunnerCLC™ configuration to allow for different areas to be controlled separately | ||
23 | * //(Optional)// Channel and threshold for enabling or disabling eDMX receiver from the third-party controller | ||
24 | ** **Default**: none (eDMX receiver is always active) | ||
25 | * //(Optional)// Add a Global Action to ShowRunnerCLC™ to enable or disable the eDMX receiver? | ||
26 | ** **Default**: no global action (eDMX receiver is always active) | ||
27 | * //(Optional)// Restrict the IP address for the eDMX receiver to listen to (i.e., provide the IP address of the third-party controller)? | ||
28 | ** **Default**: no restriction (eDMX receiver will obey commands from any IP address) | ||
29 | * //(Optional)// Port for the eDMX receiver to listen on | ||
30 | ** **Default**: 5568 (sACN) or 6454 (Art-Net) | ||
31 | |||
32 |