Differences

This shows you the differences between two versions of the page.

--- g1_lighting [2020-02-13 00:01] – welp, here goes. alfie
+++ g1_lighting [2020-02-13 22:42] – [Software (sACN Router/Proxy/Mapper/whatever)] alfie
@@ Line 14: / Line 14: @@
 ===== Eye candy =====
+===== Control =====
+==== Hardware ====
+DMX is the standard lighting control protocol. Art-net and sACN are two protocols for pushing DMX over a network. Allie has some designs for cheap sACN to DMX nodes based around the ESP8266, which have proven to be pretty reliable so far.
+==== Software (sACN Router/Proxy/Mapper/whatever) ====
+The core of the new lighting will be a control engine (probably in python) which is responsible for the following:
+  * Generating control data based on cues (presets/scenes) fired over MQTT ("office mode") or by other automations (time-of-day control, perhaps? need to figure out boundary of what this software should be responsible for)
+  * Receiving sACN raw control ("party mode") data
+  *  Intelligently(-ish) mixing/fading between office mode data and party mode data, either based on MQTT commands or priority/precedence rules.
+  * Mapping the input channel space to the output channel space (channel 73-82 of control universe 3 might map to channels 1-10 of output universe 1 of unicast sACN device 10.200.10.3, for instance)
+  * Sending sACN to the lab's lighting fixtures
+  * Exposing some form of interface/configuration language to configure the above
+This is not an insignificant amount of complexity - I would assume it would end up including some sort of DSL for creating complex architectural lighting cues, as well as maybe some form of web interface/etc.