Last modified by Alexander Mott on 2024/06/13 19:47

From version 5.1
edited by Alexander Mott
on 2024/06/13 19:41
Change comment: There is no comment for this version
To version 7.1
edited by Alexander Mott
on 2024/06/13 19:47
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -6,7 +6,7 @@
6 6  
7 7  * Third-party controller must be capable of sending eDMX commands via sACN or Art-Net
8 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]] must be added to the ShowRunnerCLC™ controlled hardware
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 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 11  ** DIN-SACN-DMX must be on the lighting control LAN/VLAN
12 12  
... ... @@ -18,6 +18,7 @@
18 18  ** If traditional DMX is used, then sACN from a DIN-SACN-DMX receiver is assumed
19 19  * **(Required)** Universe/Channel to ShowRunnerCLC™ load map
20 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
21 21  ** Multiple eDMX receivers can be defined in ShowRunnerCLC™ configuration to allow for different areas to be controlled separately
22 22  * //(Optional)// Channel and threshold for enabling or disabling eDMX receiver from the third-party controller
23 23  ** **Default**: none (eDMX receiver is always active)