OLA DMX Trigger - Revision history

Peternewman: Add migrated template

2018-06-01T02:20:00Z

Add migrated template

Peternewman: /* Sample Configs */ Fix link

2013-12-29T00:15:50Z

‎Sample Configs: Fix link

Peternewman: /* Sample Configs */ Fix configs link

2013-12-29T00:03:16Z

‎Sample Configs: Fix configs link

Mrpackethead: /* Sample Configs */

2012-09-23T09:17:10Z

‎Sample Configs

Nomis52: /* Sample Configs */

2012-01-14T17:53:08Z

‎Sample Configs

Nomis52: /* Actions */

2011-12-26T19:31:08Z

‎Actions

66.92.11.32: /* Usage */

2011-12-26T19:16:36Z

‎Usage

66.92.11.32 at 22:34, 25 December 2011

2011-12-25T22:34:45Z

Nomis52 at 17:41, 24 December 2011

2011-12-24T17:41:43Z

Nomis52 at 17:36, 24 December 2011

2011-12-24T17:36:52Z

← Older revision		Revision as of 02:20, 1 June 2018
Line 1:		Line 1:
		+	{{PageMigrated\|url=https://www.openlighting.org/ola/advanced-topics/ola-dmx-trigger/}}
	ola_trigger executes programs based on the values of DMX512 data. This allows a lighting console to trigger events on a computer, like playing music samples, advancing slides in presentations etc. . ola_trigger supports variable assignment, which offers a flexible way to control the behavior of the programs with the DMX512 data.		ola_trigger executes programs based on the values of DMX512 data. This allows a lighting console to trigger events on a computer, like playing music samples, advancing slides in presentations etc. . ola_trigger supports variable assignment, which offers a flexible way to control the behavior of the programs with the DMX512 data.

← Older revision		Revision as of 00:15, 29 December 2013
Line 138:		Line 138:
	A full example config is provided in the tools/ola_trigger directory. If you have configs that may be useful to others please submit them.		A full example config is provided in the tools/ola_trigger directory. If you have configs that may be useful to others please submit them.

−	[[Raspberry PI Media Player]] A combination of a Raspberry PI, ola_trigger and omxplayer	+	[[Raspberry Pi Media Player]] A combination of a Raspberry PI, ola_trigger and omxplayer

@@ Line 134: / Line 134: @@
 = Sample Configs =
-Sample configs are provided in the [http://code.google.com/p/linux-lighting/source/browse/#git%2Ftools%2Fola_trigger%2Fcontrib tools/ola_trigger/contrib] directory.
+Sample configs are provided in the [https://github.com/OpenLightingProject/ola/tree/master/tools/ola_trigger/contrib tools/ola_trigger/contrib] directory.
 A full example config is provided in the tools/ola_trigger directory. If you have configs that may be useful to others please submit them.
-[[Rasberry PI Media Player]] A combination of a Raspberry PI, ola_trigger and omxplayer
+[[Raspberry PI Media Player]] A combination of a Raspberry PI, ola_trigger and omxplayer

← Older revision		Revision as of 09:17, 23 September 2012
Line 137:		Line 137:

	A full example config is provided in the tools/ola_trigger directory. If you have configs that may be useful to others please submit them.		A full example config is provided in the tools/ola_trigger directory. If you have configs that may be useful to others please submit them.
		+
		+	[[Rasberry PI Media Player]] A combination of a Raspberry PI, ola_trigger and omxplayer

← Older revision		Revision as of 17:53, 14 January 2012
Line 137:		Line 137:

	A full example config is provided in the tools/ola_trigger directory. If you have configs that may be useful to others please submit them.		A full example config is provided in the tools/ola_trigger directory. If you have configs that may be useful to others please submit them.
−
−
−
−	~~<pre>~~
−	~~# Example DMX Trigger Config File~~
−
−	~~# Variable definitions~~
−	~~###############################################################################~~
−	~~# The default value of slot 2, this won't ever be used, since the variable is~~
−	~~# only used with slot 3, which implies we already got data for slot 2.~~
−	~~slot_2_value = "nan" # nan isn't special in any way~~
−
−	~~# Triggers~~
−	~~###############################################################################~~
−	~~# Slot Trigger Values Action~~
−
−	~~# Slot 0 prints the current value of slot 0~~
−	~~0 % `echo "Slot ${slot_offset} is at ${slot_value}"`~~
−
−	~~# Slot 1 runs a different command line tools~~
−	~~1 1 `ls`~~
−	~~1 2 `ps aux`~~
−	~~1 3 `who`~~
−
−	~~# Slot 2 sets a variable~~
−	~~2 % slot_2_value="${slot_value}"~~
−
−	~~# Slot 3 prints the value of slot2 if slot3 is greater than 50%~~
−	~~3 128-255 `echo "Previous slot is ${slot_2_value}"`~~
−	~~</pre>~~

@@ Line 41: / Line 41: @@
 === Actions ===
-The third column specifies the action to run. Actions can be either variable assignments or commands.
+The third column specifies the action to run. Actions can be either variable assignments or commands and can trigger on rising values, falling values or both.
 ==== Variable Assignment ====
@@ Line 78: / Line 78: @@
 `echo ${count_${i}}`   # runs echo foo
 </pre>
 === Full Action Definition Example ===

@@ Line 116: / Line 116: @@
 Some useful options include:
 ; -l, --log-level <level>
-: This change the logging level, valid values are 0 (minimum logging) to 4 (full logs).
+: This change the logging level, valid values are 0 (minimum logging) to 4 (full logs). At log level 3 (INFO) and above, all actions (variable assignments and commands) will be logged.
 ;-o, --offset <slot_offset>
 : This applies an offset to the configured slots. For example if the config file contains definitions for slots 0 and 1, if ola_trigger is run with -o 10 it will watch for values on slots 10 and 11. Defaults to 0.

@@ Line 122: / Line 122: @@
 : Specifies the universe to use. Defaults to 1.
-= Example =
+= Sample Configs =
 <pre>

@@ Line 3: / Line 3: @@
 = Config File Syntax =
-The config file defines the mapping of slot values to actions. Each line is a directive and directives are either ''action definitions'' or ''variable assignment''. The order of directives within the config file doesn't matter - actions are trigger in the order of their slot numbers.
+The config file defines the mapping of slot values to actions. Each line is a directive and directives are either ''action definitions'' or ''variable assignment''. The order of directives within the config file doesn't matter - actions are triggered in the order of their slot numbers.
 Any characters between a '#' and the end of the line are comments and are ignored.
@@ Line 12: / Line 12: @@
 <pre>
-[Slot Number]    [Slot Values]   [Action]
+[Slot Number]   [Slot Values]   [Action]
 </pre>
@@ Line 19: / Line 19: @@
 === Slot Number ===
-The first column, slot number, specifies the DMX512 slot the action is valid for. Slot numbers range from 0 to 511. Slot numbers may be offset by using the --offset option (see the Usage section above).
+The first column, slot number, specifies the DMX512 slot the action is valid for. Slot numbers range from 0 to 511. Slot numbers may be offset by using the --offset option (see the Usage section below).
 === Slot Values ===
-The second column controls which DMX512 values trigger the action.  Slot values range from 0 to 255.
+The second column controls which DMX512 values trigger the action.  Slot values range from 0 to 255. Multiple values are separated by commas. Ranges can be specified with a hyphen.
 <pre>
-,2,3,4   # Trigger on values 1 through to 4
+,2,3,4   # Values 1 through to 4
--4,10-14 # Trigger on values 1 to 4 and 10 to 14 (inclusive)
+-4,10-14 # Values 1 to 4 and 10 to 14 (inclusive)
 </pre>
@@ Line 36: / Line 34: @@
 <pre>
 -100  # Values 0 to 100
-%         # Triggers for everything else (101 - 255)
+%      # Triggers for everything else (101 - 255)
 </pre>
@@ Line 53: / Line 51: @@
 </pre>
-The value can be quoted:
+The value must be quoted if it contains whitespace:
 <pre>
@@ Line 103: / Line 101: @@
 <pre>
-        %                `echo "Slot ${slot_offset} is at ${slot_value}"`
+   %   `echo "Slot ${slot_offset} is at ${slot_value}"`
 </pre>
@@ Line 152: / Line 150: @@
          %                slot_2_value="${slot_value}"
-# Slot 3 prints the value of slot3 if slot3 is greater than 50%
+# Slot 3 prints the value of slot2 if slot3 is greater than 50%
-         128-255          `echo "Slot 2 is ${slot_2_value}"`
+         128-255          `echo "Previous slot is ${slot_2_value}"`
 </pre>