<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
		<id>https://wiki.openlighting.org/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Nightrune</id>
		<title>wiki.openlighting.org - User contributions [en]</title>
		<link rel="self" type="application/atom+xml" href="https://wiki.openlighting.org/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Nightrune"/>
		<link rel="alternate" type="text/html" href="https://wiki.openlighting.org/index.php/Special:Contributions/Nightrune"/>
		<updated>2026-04-28T20:48:53Z</updated>
		<subtitle>User contributions</subtitle>
		<generator>MediaWiki 1.29.1</generator>

	<entry>
		<id>https://wiki.openlighting.org/index.php?title=Building_OLA_for_Windows&amp;diff=5762</id>
		<title>Building OLA for Windows</title>
		<link rel="alternate" type="text/html" href="https://wiki.openlighting.org/index.php?title=Building_OLA_for_Windows&amp;diff=5762"/>
				<updated>2014-11-30T21:26:52Z</updated>
		
		<summary type="html">&lt;p&gt;Nightrune: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This describes how to get OLA compiled for windows, it's a work in progress so it's unlikely to work as is. This tutorial uses gcc as the compiler, other compilers have not been tested.&lt;br /&gt;
&lt;br /&gt;
During [[GSOC2014WindowsPort|Google Summer of Code 2014]], this port will be worked on as one of the selected projects.&lt;br /&gt;
&lt;br /&gt;
== Install Mingw, msys &amp;amp; build tools ==&lt;br /&gt;
&lt;br /&gt;
Together MinGW &amp;amp; msys provide a unix-style shell environment &amp;amp; compiler suite for windows. Read the instructions at the [http://www.mingw.org/ MinGW] site for more info. MinGW now provides an installer to get most of the system up and running quickly. [http://sourceforge.net/projects/mingw/files/Automated%20MinGW%20Installer/mingw-get-inst/ Download] the installer and make sure you select &amp;quot;C++ Compiler&amp;quot;. &amp;quot;MSYS Basic System&amp;quot; &amp;amp; &amp;quot;MinGW Developer Toolkit&amp;quot; when prompted.&lt;br /&gt;
&lt;br /&gt;
Once the installer has completed, open the msys shell (under Programs &amp;gt; MinGW) and install some additional packages:&lt;br /&gt;
&lt;br /&gt;
 $ mingw-get.exe install msys-coreutils mingw32-base mingw32-pthreads-w32 msys-wget&lt;br /&gt;
&lt;br /&gt;
Note that some of these might already have been installed.&lt;br /&gt;
&lt;br /&gt;
== Install Git ==&lt;br /&gt;
&lt;br /&gt;
Git is used to checkout (and commit) the ola sources.  See http://code.google.com/p/msysgit/, be sure to select &amp;quot;checkout as is, commit unix style&amp;quot; during the install otherwise you'll get autoconf errors.&lt;br /&gt;
&lt;br /&gt;
Add the following line to your .bashrc file so that git can be used within msys:&lt;br /&gt;
&lt;br /&gt;
 PATH=&amp;quot;$PATH:/c/Program Files/Git/bin&amp;quot;&lt;br /&gt;
 alias git=git.exe&lt;br /&gt;
&lt;br /&gt;
If you are on 64bit windows you may need to use:&lt;br /&gt;
&lt;br /&gt;
 PATH=&amp;quot;$PATH:/c/Program Files (x86)/Git/bin&amp;quot;&lt;br /&gt;
 alias git=git.exe&lt;br /&gt;
&lt;br /&gt;
== Install pkg-config ==&lt;br /&gt;
&lt;br /&gt;
Download pkg-config-lite from http://sourceforge.net/projects/pkgconfiglite/files/ (the latest binary should work) and extract it to your MinGW directory.&lt;br /&gt;
&lt;br /&gt;
You also need to add&lt;br /&gt;
&lt;br /&gt;
  export PKG_CONFIG_PATH=/usr/local/lib/pkgconfig&lt;br /&gt;
  CPPFLAGS=&amp;quot;-I/usr/local/include&amp;quot;&lt;br /&gt;
  LDFLAGS=&amp;quot;-L/usr/local/lib&amp;quot;&lt;br /&gt;
&lt;br /&gt;
to your .bashrc file.&lt;br /&gt;
&lt;br /&gt;
You might also want to edit your .profile file and add &amp;lt;pre&amp;gt;[ -f ~/.bashrc ] &amp;amp;&amp;amp; . ~/.bashrc&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If you haven't configured your MSYS fstab yet, do that as well. See http://www.mingw.org/wiki/Getting_Started for instructions.&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
== Install Dependencies ==&lt;br /&gt;
&lt;br /&gt;
=== pkg-config ===&lt;br /&gt;
* Download pkg-config-lite from http://sourceforge.net/projects/pkgconfiglite/files/&lt;br /&gt;
* Extract to MinGW directory&lt;br /&gt;
&lt;br /&gt;
=== Python (optional) ===&lt;br /&gt;
* Tested version: 2.7 series&lt;br /&gt;
* Download and install Python for Windows from https://www.python.org/downloads/&lt;br /&gt;
&lt;br /&gt;
=== msys-git ===&lt;br /&gt;
* Download msysgit from https://code.google.com/p/msysgit/downloads/list&lt;br /&gt;
* Install and make sure to select &amp;quot;Check-out as is, commit UNIX-style&amp;quot;&lt;br /&gt;
&lt;br /&gt;
=== libuuid ===&lt;br /&gt;
* Download and extract the latest libuuid tarball from https://code.google.com/p/gnome-build-stage-1/downloads/list&lt;br /&gt;
* Configure, compile and install it using the MinGW MSYS shell&lt;br /&gt;
&lt;br /&gt;
=== protobuf ===&lt;br /&gt;
* Download and extract the latest protobuf tarball from https://code.google.com/p/protobuf/downloads/list&lt;br /&gt;
* Configure, compile and install it using the MinGW MSYS shell&lt;br /&gt;
* if you want to use the OLA Python api, install the protobuf Python bindings from the 'python' subdirectory&lt;br /&gt;
&lt;br /&gt;
=== cppunit ===&lt;br /&gt;
* Download and extract the latest cppunit tarball from http://sourceforge.net/projects/cppunit/files/cppunit/&lt;br /&gt;
* Configure, compile and install it using the MinGW MSYS shell&lt;br /&gt;
&lt;br /&gt;
=== libmicrohttpd ===&lt;br /&gt;
* Download and extract the latest libmicrohttpd tarball from http://ftp.gnu.org/gnu/libmicrohttpd/&lt;br /&gt;
* Configure, compile and install it using the MinGW MSYS shell&lt;br /&gt;
&lt;br /&gt;
=== liblo (optional) ===&lt;br /&gt;
* Download and extract the latest version of liblo from http://liblo.sourceforge.net/&lt;br /&gt;
* Configure, compile and install it using the MinGW MSYS shell&lt;br /&gt;
&lt;br /&gt;
== Build OLA ==&lt;br /&gt;
&lt;br /&gt;
* Do a git checkout of OLA&lt;br /&gt;
&lt;br /&gt;
  $ git.exe clone https://github.com/OpenLightingProject/ola.git&lt;br /&gt;
&lt;br /&gt;
* Prepare autotools files&lt;br /&gt;
  $ autoreconf -i -f&lt;br /&gt;
&lt;br /&gt;
* Run ./configure&lt;br /&gt;
  $ ./configure --enable-python-libs --disable-e131 --disable-karate --disable-milinst --disable-renard --disable-spi --disable-stageprofi --disable-usbpro --disable-usbdmx --disable-uart&lt;br /&gt;
&lt;br /&gt;
* Build&lt;br /&gt;
  $ make&lt;br /&gt;
&lt;br /&gt;
* Optional: Run the tests&lt;br /&gt;
  $ make check&lt;br /&gt;
&lt;br /&gt;
* Install&lt;br /&gt;
  $ make install&lt;br /&gt;
&lt;br /&gt;
== Current State / TODO ==&lt;br /&gt;
&lt;br /&gt;
See the [[GSOC2014WindowsPort|GSOC project page]].&lt;br /&gt;
&lt;br /&gt;
== Misc Notes ==&lt;br /&gt;
&lt;br /&gt;
You may run into issues with the latest mingw and protobufs. During runtime it can't find libstdc++-6.dll. Attempt to follow this and see if any of the solutions fixes your problem. We'd love to hear the outcome on irc or the forums.&lt;br /&gt;
http://stackoverflow.com/questions/6404636/libstdc-6-dll-not-found&lt;br /&gt;
&lt;br /&gt;
Sean Sill:&lt;br /&gt;
I ended up removing libstdc++.dll.a from the C:/MinGW/libs folder.&lt;/div&gt;</summary>
		<author><name>Nightrune</name></author>	</entry>

	<entry>
		<id>https://wiki.openlighting.org/index.php?title=Building_OLA_for_Windows&amp;diff=5761</id>
		<title>Building OLA for Windows</title>
		<link rel="alternate" type="text/html" href="https://wiki.openlighting.org/index.php?title=Building_OLA_for_Windows&amp;diff=5761"/>
				<updated>2014-11-30T21:20:04Z</updated>
		
		<summary type="html">&lt;p&gt;Nightrune: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This describes how to get OLA compiled for windows, it's a work in progress so it's unlikely to work as is. This tutorial uses gcc as the compiler, other compilers have not been tested.&lt;br /&gt;
&lt;br /&gt;
During [[GSOC2014WindowsPort|Google Summer of Code 2014]], this port will be worked on as one of the selected projects.&lt;br /&gt;
&lt;br /&gt;
== Install Mingw, msys &amp;amp; build tools ==&lt;br /&gt;
&lt;br /&gt;
Together MinGW &amp;amp; msys provide a unix-style shell environment &amp;amp; compiler suite for windows. Read the instructions at the [http://www.mingw.org/ MinGW] site for more info. MinGW now provides an installer to get most of the system up and running quickly. [http://sourceforge.net/projects/mingw/files/Automated%20MinGW%20Installer/mingw-get-inst/ Download] the installer and make sure you select &amp;quot;C++ Compiler&amp;quot;. &amp;quot;MSYS Basic System&amp;quot; &amp;amp; &amp;quot;MinGW Developer Toolkit&amp;quot; when prompted.&lt;br /&gt;
&lt;br /&gt;
Once the installer has completed, open the msys shell (under Programs &amp;gt; MinGW) and install some additional packages:&lt;br /&gt;
&lt;br /&gt;
 $ mingw-get.exe install msys-coreutils mingw32-base mingw32-pthreads-w32 msys-wget&lt;br /&gt;
&lt;br /&gt;
Note that some of these might already have been installed.&lt;br /&gt;
&lt;br /&gt;
== Install Git ==&lt;br /&gt;
&lt;br /&gt;
Git is used to checkout (and commit) the ola sources.  See http://code.google.com/p/msysgit/, be sure to select &amp;quot;checkout as is, commit unix style&amp;quot; during the install otherwise you'll get autoconf errors.&lt;br /&gt;
&lt;br /&gt;
Add the following line to your .bashrc file so that git can be used within msys:&lt;br /&gt;
&lt;br /&gt;
 PATH=&amp;quot;$PATH:/c/Program Files/Git/bin&amp;quot;&lt;br /&gt;
 alias git=git.exe&lt;br /&gt;
&lt;br /&gt;
If you are on 64bit windows you may need to use:&lt;br /&gt;
&lt;br /&gt;
 PATH=&amp;quot;$PATH:/c/Program Files (x86)/Git/bin&amp;quot;&lt;br /&gt;
 alias git=git.exe&lt;br /&gt;
&lt;br /&gt;
== Install pkg-config ==&lt;br /&gt;
&lt;br /&gt;
Download pkg-config-lite from http://sourceforge.net/projects/pkgconfiglite/files/ (the latest binary should work) and extract it to your MinGW directory.&lt;br /&gt;
&lt;br /&gt;
You also need to add&lt;br /&gt;
&lt;br /&gt;
  export PKG_CONFIG_PATH=/usr/local/lib/pkgconfig&lt;br /&gt;
  CPPFLAGS=&amp;quot;-I/usr/local/include&amp;quot;&lt;br /&gt;
  LDFLAGS=&amp;quot;-L/usr/local/lib&amp;quot;&lt;br /&gt;
&lt;br /&gt;
to your .bashrc file.&lt;br /&gt;
&lt;br /&gt;
You might also want to edit your .profile file and add &amp;lt;pre&amp;gt;[ -f ~/.bashrc ] &amp;amp;&amp;amp; . ~/.bashrc&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If you haven't configured your MSYS fstab yet, do that as well. See http://www.mingw.org/wiki/Getting_Started for instructions.&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
== Install Dependencies ==&lt;br /&gt;
&lt;br /&gt;
=== pkg-config ===&lt;br /&gt;
* Download pkg-config-lite from http://sourceforge.net/projects/pkgconfiglite/files/&lt;br /&gt;
* Extract to MinGW directory&lt;br /&gt;
&lt;br /&gt;
=== Python (optional) ===&lt;br /&gt;
* Tested version: 2.7 series&lt;br /&gt;
* Download and install Python for Windows from https://www.python.org/downloads/&lt;br /&gt;
&lt;br /&gt;
=== msys-git ===&lt;br /&gt;
* Download msysgit from https://code.google.com/p/msysgit/downloads/list&lt;br /&gt;
* Install and make sure to select &amp;quot;Check-out as is, commit UNIX-style&amp;quot;&lt;br /&gt;
&lt;br /&gt;
=== libuuid ===&lt;br /&gt;
* Download and extract the latest libuuid tarball from https://code.google.com/p/gnome-build-stage-1/downloads/list&lt;br /&gt;
* Configure, compile and install it using the MinGW MSYS shell&lt;br /&gt;
&lt;br /&gt;
=== protobuf ===&lt;br /&gt;
* Download and extract the latest protobuf tarball from https://code.google.com/p/protobuf/downloads/list&lt;br /&gt;
* Configure, compile and install it using the MinGW MSYS shell&lt;br /&gt;
* if you want to use the OLA Python api, install the protobuf Python bindings from the 'python' subdirectory&lt;br /&gt;
&lt;br /&gt;
=== cppunit ===&lt;br /&gt;
* Download and extract the latest cppunit tarball from http://sourceforge.net/projects/cppunit/files/cppunit/&lt;br /&gt;
* Configure, compile and install it using the MinGW MSYS shell&lt;br /&gt;
&lt;br /&gt;
=== libmicrohttpd ===&lt;br /&gt;
* Download and extract the latest libmicrohttpd tarball from http://ftp.gnu.org/gnu/libmicrohttpd/&lt;br /&gt;
* Configure, compile and install it using the MinGW MSYS shell&lt;br /&gt;
&lt;br /&gt;
=== liblo (optional) ===&lt;br /&gt;
* Download and extract the latest version of liblo from http://liblo.sourceforge.net/&lt;br /&gt;
* Configure, compile and install it using the MinGW MSYS shell&lt;br /&gt;
&lt;br /&gt;
== Build OLA ==&lt;br /&gt;
&lt;br /&gt;
* Do a git checkout of OLA&lt;br /&gt;
&lt;br /&gt;
  $ git.exe clone https://github.com/OpenLightingProject/ola.git&lt;br /&gt;
&lt;br /&gt;
* Prepare autotools files&lt;br /&gt;
  $ autoreconf -i -f&lt;br /&gt;
&lt;br /&gt;
* Run ./configure&lt;br /&gt;
  $ ./configure --enable-python-libs --disable-e131 --disable-karate --disable-milinst --disable-renard --disable-spi --disable-stageprofi --disable-usbpro --disable-usbdmx --disable-uart&lt;br /&gt;
&lt;br /&gt;
* Build&lt;br /&gt;
  $ make&lt;br /&gt;
&lt;br /&gt;
* Optional: Run the tests&lt;br /&gt;
  $ make check&lt;br /&gt;
&lt;br /&gt;
* Install&lt;br /&gt;
  $ make install&lt;br /&gt;
&lt;br /&gt;
== Current State / TODO ==&lt;br /&gt;
&lt;br /&gt;
See the [[GSOC2014WindowsPort|GSOC project page]].&lt;br /&gt;
&lt;br /&gt;
== Misc Notes ==&lt;br /&gt;
&lt;br /&gt;
You may run into issues with the latest mingw and protobufs. During runtime it can't find libstdc++-6.dll. Attempt to follow this and see if any of the solutions fixes your problem. We'd love to hear the outcome on irc or the forums.&lt;br /&gt;
http://stackoverflow.com/questions/6404636/libstdc-6-dll-not-found&lt;/div&gt;</summary>
		<author><name>Nightrune</name></author>	</entry>

	<entry>
		<id>https://wiki.openlighting.org/index.php?title=Building_OLA_for_Windows&amp;diff=5754</id>
		<title>Building OLA for Windows</title>
		<link rel="alternate" type="text/html" href="https://wiki.openlighting.org/index.php?title=Building_OLA_for_Windows&amp;diff=5754"/>
				<updated>2014-11-11T12:36:47Z</updated>
		
		<summary type="html">&lt;p&gt;Nightrune: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This describes how to get OLA compiled for windows, it's a work in progress so it's unlikely to work as is. This tutorial uses gcc as the compiler, other compilers have not been tested.&lt;br /&gt;
&lt;br /&gt;
During [[GSOC2014WindowsPort|Google Summer of Code 2014]], this port will be worked on as one of the selected projects.&lt;br /&gt;
&lt;br /&gt;
== Install Mingw, msys &amp;amp; build tools ==&lt;br /&gt;
&lt;br /&gt;
Together MinGW &amp;amp; msys provide a unix-style shell environment &amp;amp; compiler suite for windows. Read the instructions at the [http://www.mingw.org/ MinGW] site for more info. MinGW now provides an installer to get most of the system up and running quickly. [http://sourceforge.net/projects/mingw/files/Automated%20MinGW%20Installer/mingw-get-inst/ Download] the installer and make sure you select &amp;quot;C++ Compiler&amp;quot;. &amp;quot;MSYS Basic System&amp;quot; &amp;amp; &amp;quot;MinGW Developer Toolkit&amp;quot; when prompted.&lt;br /&gt;
&lt;br /&gt;
Once the installer has completed, open the msys shell (under Programs &amp;gt; MinGW) and install some additional packages:&lt;br /&gt;
&lt;br /&gt;
 $ mingw-get.exe install msys-coreutils mingw32-base mingw32-pthreads-w32 msys-wget&lt;br /&gt;
&lt;br /&gt;
Note that some of these might already have been installed.&lt;br /&gt;
&lt;br /&gt;
== Install Git ==&lt;br /&gt;
&lt;br /&gt;
Git is used to checkout (and commit) the ola sources.  See http://code.google.com/p/msysgit/, be sure to select &amp;quot;checkout as is, commit unix style&amp;quot; during the install otherwise you'll get autoconf errors.&lt;br /&gt;
&lt;br /&gt;
Add the following line to your .bashrc file so that git can be used within msys:&lt;br /&gt;
&lt;br /&gt;
 PATH=&amp;quot;$PATH:/c/Program Files/Git/bin&amp;quot;&lt;br /&gt;
 alias git=git.exe&lt;br /&gt;
&lt;br /&gt;
If you are on 64bit windows you may need to use:&lt;br /&gt;
&lt;br /&gt;
 PATH=&amp;quot;$PATH:/c/Program Files (x86)/Git/bin&amp;quot;&lt;br /&gt;
 alias git=git.exe&lt;br /&gt;
&lt;br /&gt;
== Install pkg-config ==&lt;br /&gt;
&lt;br /&gt;
Download pkg-config-lite from http://sourceforge.net/projects/pkgconfiglite/files/ (the latest binary should work) and extract it to your MinGW directory.&lt;br /&gt;
&lt;br /&gt;
You also need to add&lt;br /&gt;
&lt;br /&gt;
  export PKG_CONFIG_PATH=/usr/local/lib/pkgconfig&lt;br /&gt;
  CPPFLAGS=&amp;quot;-I/usr/local/include&amp;quot;&lt;br /&gt;
  LDFLAGS=&amp;quot;-L/usr/local/lib&amp;quot;&lt;br /&gt;
&lt;br /&gt;
to your .bashrc file.&lt;br /&gt;
&lt;br /&gt;
You might also want to edit your .profile file and add &amp;lt;pre&amp;gt;[ -f ~/.bashrc ] &amp;amp;&amp;amp; . ~/.bashrc&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If you haven't configured your MSYS fstab yet, do that as well. See http://www.mingw.org/wiki/Getting_Started for instructions.&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
== Install Dependencies ==&lt;br /&gt;
&lt;br /&gt;
=== pkg-config ===&lt;br /&gt;
* Download pkg-config-lite from http://sourceforge.net/projects/pkgconfiglite/files/&lt;br /&gt;
* Extract to MinGW directory&lt;br /&gt;
&lt;br /&gt;
=== Python (optional) ===&lt;br /&gt;
* Tested version: 2.7 series&lt;br /&gt;
* Download and install Python for Windows from https://www.python.org/downloads/&lt;br /&gt;
&lt;br /&gt;
=== msys-git ===&lt;br /&gt;
* Download msysgit from https://code.google.com/p/msysgit/downloads/list&lt;br /&gt;
* Install and make sure to select &amp;quot;Check-out as is, commit UNIX-style&amp;quot;&lt;br /&gt;
&lt;br /&gt;
=== libuuid ===&lt;br /&gt;
* Download and extract the latest libuuid tarball from https://code.google.com/p/gnome-build-stage-1/downloads/list&lt;br /&gt;
* Configure, compile and install it using the MinGW MSYS shell&lt;br /&gt;
&lt;br /&gt;
=== protobuf ===&lt;br /&gt;
* Download and extract the latest protobuf tarball from https://code.google.com/p/protobuf/downloads/list&lt;br /&gt;
* Configure, compile and install it using the MinGW MSYS shell&lt;br /&gt;
* if you want to use the OLA Python api, install the protobuf Python bindings from the 'python' subdirectory&lt;br /&gt;
&lt;br /&gt;
=== cppunit ===&lt;br /&gt;
* Download and extract the latest cppunit tarball from http://sourceforge.net/projects/cppunit/files/cppunit/&lt;br /&gt;
* Configure, compile and install it using the MinGW MSYS shell&lt;br /&gt;
&lt;br /&gt;
=== libmicrohttpd ===&lt;br /&gt;
* Download and extract the latest libmicrohttpd tarball from http://ftp.gnu.org/gnu/libmicrohttpd/&lt;br /&gt;
* Configure, compile and install it using the MinGW MSYS shell&lt;br /&gt;
&lt;br /&gt;
=== liblo (optional) ===&lt;br /&gt;
* Download and extract the latest version of liblo from http://liblo.sourceforge.net/&lt;br /&gt;
* Configure, compile and install it using the MinGW MSYS shell&lt;br /&gt;
&lt;br /&gt;
== Build OLA ==&lt;br /&gt;
&lt;br /&gt;
* Do a git checkout of OLA&lt;br /&gt;
&lt;br /&gt;
  $ git.exe clone https://github.com/OpenLightingProject/ola.git&lt;br /&gt;
&lt;br /&gt;
* Prepare autotools files&lt;br /&gt;
  $ autoreconf -i -f&lt;br /&gt;
&lt;br /&gt;
* Run ./configure&lt;br /&gt;
  $ ./configure --enable-python-libs --disable-e131 --disable-karate --disable-milinst --disable-renard --disable-spi --disable-stageprofi --disable-usbpro --disable-usbdmx --disable-uart&lt;br /&gt;
&lt;br /&gt;
* Build&lt;br /&gt;
  $ make&lt;br /&gt;
&lt;br /&gt;
* Optional: Run the tests&lt;br /&gt;
  $ make check&lt;br /&gt;
&lt;br /&gt;
* Install&lt;br /&gt;
  $ make install&lt;br /&gt;
&lt;br /&gt;
== Current State / TODO ==&lt;br /&gt;
&lt;br /&gt;
See the [[GSOC2014WindowsPort|GSOC project page]].&lt;/div&gt;</summary>
		<author><name>Nightrune</name></author>	</entry>

	<entry>
		<id>https://wiki.openlighting.org/index.php?title=Open_Lighting_Project&amp;diff=5668</id>
		<title>Open Lighting Project</title>
		<link rel="alternate" type="text/html" href="https://wiki.openlighting.org/index.php?title=Open_Lighting_Project&amp;diff=5668"/>
				<updated>2014-03-02T00:30:58Z</updated>
		
		<summary type="html">&lt;p&gt;Nightrune: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;The Open Lighting Project is a multi-faceted effort aimed at accelerating the adoption of new, standardized control protocols, while also providing high quality, reliable, open software for the lighting industry. This site acts as a resource for anyone looking for information about DMX software and the associated control systems, as well as a variety of Open Source and free lighting software.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;table style=&amp;quot;width: 100%; margin:4px 0 0 0; background:none; border-spacing: 5px;&amp;quot;&amp;gt;&lt;br /&gt;
 &amp;lt;tr&amp;gt;&lt;br /&gt;
  &amp;lt;td style=&amp;quot;width:45%; border:1px solid #cedff2; background:#f5faff; vertical-align:top; padding: 4px&amp;quot;&amp;gt;&lt;br /&gt;
    [[Image:OLA-Logo-Fitted-48px.png|right|link=OLA]]&lt;br /&gt;
    &amp;lt;h2 style=&amp;quot;float:left; font-size:120%; padding: .2em; margin:3px; font-weight:bold;&amp;quot;&amp;gt;[[OLA | The Open Lighting Architecture]]&amp;lt;/h2&amp;gt;&lt;br /&gt;
    &amp;lt;div style=&amp;quot;clear: left&amp;quot;&amp;gt;&lt;br /&gt;
The [[OLA | Open Lighting Architecture]] provides a framework for distributing lighting control information. It supports many protocols such as E1.31 (sACN), ArtNet, ShowNet, Pathport, RDM and over a dozen USB devices. It can run as a standalone service, which is useful for converting signals between protocols, or alternatively it can be used as the backend for [[:Category:Controllers | Controller Applications]]. OLA runs on many different platforms including ARM, which makes it a perfect fit for low cost Ethernet to DMX gateways.&lt;br /&gt;
    &amp;lt;/div&amp;gt;&lt;br /&gt;
  &amp;lt;/td&amp;gt;&lt;br /&gt;
  &amp;lt;td style=&amp;quot;width:45%; border:1px solid #cedff2; background:#f5faff; vertical-align:top; padding: 4px&amp;quot;&amp;gt;&lt;br /&gt;
    [[Image:rdm-logo-small.png|right|link=]]&lt;br /&gt;
    &amp;lt;h2 style=&amp;quot;float:left; font-size:120%; padding: .2em; margin:3px; font-weight:bold;&amp;quot;&amp;gt;[[RDM_Responder_Testing | RDM Responder Tests]]&amp;lt;/h2&amp;gt;&lt;br /&gt;
    &amp;lt;div style=&amp;quot;clear: left&amp;quot;&amp;gt;&lt;br /&gt;
Testing RDM Responder used to involve manually sending commands and verifying the responses. Not any longer! The [[RDM_Responder_Testing | RDM Responder Tests]] automate all of this and provide a detailed breakdown of how well a responder complies with the [[E1.20]] (RDM) standard. This saves time during the product development process and raises the quality of RDM implementations across the industry.&lt;br /&gt;
&lt;br /&gt;
For questions about the RDM Responder tests, email the  [http://groups.google.com/group/rdm-testing RDM Testing List].&lt;br /&gt;
    &amp;lt;/div&amp;gt;&lt;br /&gt;
  &amp;lt;/td&amp;gt;&lt;br /&gt;
 &amp;lt;/tr&amp;gt;&lt;br /&gt;
 &amp;lt;tr&amp;gt;&amp;lt;td colspan=&amp;quot;2&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
 &amp;lt;tr&amp;gt;&lt;br /&gt;
  &amp;lt;td style=&amp;quot;width:45%; border:1px solid #cedff2; background:#f5faff; vertical-align:top; padding: 4px&amp;quot;&amp;gt;&lt;br /&gt;
    [[Image:raspi-logo-small.png|right|link=]]&lt;br /&gt;
    &amp;lt;h2 style=&amp;quot;float:left; font-size:120%; padding: .2em; margin:3px; font-weight:bold;&amp;quot;&amp;gt;[[OLA_Raspberry_Pi | OLA on the Raspberry Pi]]&amp;lt;/h2&amp;gt;&lt;br /&gt;
    &amp;lt;div style=&amp;quot;clear: left&amp;quot;&amp;gt;&lt;br /&gt;
The [http://www.raspberrypi.org/ Raspberry Pi] is one of the most popular platforms for running [[OLA]]. With the addition of a USB to DMX device, one can build a low cost, but fully functional Ethernet gateway. The [[OLA_Raspberry_Pi | OLA on Raspberry Pi]] tutorial has a step by step guide to installing OLA on the Pi.&lt;br /&gt;
    &amp;lt;/div&amp;gt;&lt;br /&gt;
  &amp;lt;/td&amp;gt;&lt;br /&gt;
&lt;br /&gt;
  &amp;lt;td style=&amp;quot;width:45%; border:1px solid #cedff2; background:#f5faff; vertical-align:top; padding: 4px&amp;quot;&amp;gt;&lt;br /&gt;
    [[Image:Robin-1200.png|right|link=]]&lt;br /&gt;
    &amp;lt;h2 style=&amp;quot;float:left; font-size:120%; padding: .2em; margin:3px; font-weight:bold;&amp;quot;&amp;gt;rdm.openlighting.org&amp;lt;/h2&amp;gt;&lt;br /&gt;
    &amp;lt;div style=&amp;quot;clear: left&amp;quot;&amp;gt;&lt;br /&gt;
The http://rdm.openlighting.org site contains an index of RDM-enabled products as well as the specifications for many of the manufacturer specific PIDs. The site has recently been expanded to display the results of the RDM Responder Tests. The data on the site is available free of charge through APIs. &lt;br /&gt;
    &amp;lt;/div&amp;gt;&lt;br /&gt;
  &amp;lt;/td&amp;gt;&lt;br /&gt;
 &amp;lt;/tr&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td colspan=&amp;quot;2&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
 &amp;lt;tr&amp;gt;&lt;br /&gt;
  &amp;lt;td style=&amp;quot;width:45%; border:1px solid #cedff2; background:#f5faff; vertical-align:top; padding: 4px&amp;quot;&amp;gt;&lt;br /&gt;
    [[Image:Email-icon.png|right|link=]]&lt;br /&gt;
    &amp;lt;h2 style=&amp;quot;float:left; font-size:120%; padding: .2em; margin:3px; font-weight:bold;&amp;quot;&amp;gt;Contact / Support&amp;lt;/h2&amp;gt;&lt;br /&gt;
    &amp;lt;div style=&amp;quot;clear: left&amp;quot;&amp;gt;&lt;br /&gt;
Since this is an Open Source project, there is no commercial support for our products at this time. There are a number of ways of reaching the community though:&lt;br /&gt;
&lt;br /&gt;
* Primary User &amp;amp; Developer Discussion [http://groups.google.com/group/open-lighting Open Lighting Discuss] (typically a few messages per day).&lt;br /&gt;
* Announcements are posted to [http://groups.google.com/group/open-lighting-announce Open Lighting Announce] (low volume, typically 1-2 per month)&lt;br /&gt;
* RDM Testing Discussion [http://groups.google.com/group/rdm-testing RDM Testing].&lt;br /&gt;
* IRC #openlighting on freenode.net (or [http://webchat.freenode.net/?channels=openlighting webchat])&lt;br /&gt;
There is also an [https://plus.google.com/106460627923808853381 Open Lighting Community] on Google+. This is less OLA centric and more about sharing cool lighting projects people are working on. We also have a cafepress store where you can buy OLA t-shirts, stickers, and a few other random things. Visit [http://www.cafepress.com/openlighting Open Lighting at Cafepress]! Prices may change in the future. &lt;br /&gt;
    &amp;lt;/div&amp;gt;&lt;br /&gt;
  &amp;lt;/td&amp;gt;&lt;br /&gt;
&lt;br /&gt;
  &amp;lt;td style=&amp;quot;width:45%; border:1px solid #cedff2; background:#f5faff; vertical-align:top; padding: 4px&amp;quot;&amp;gt;&lt;br /&gt;
    &amp;lt;h2 style=&amp;quot;float:left; font-size:120%; padding: .2em; margin:3px; font-weight:bold;&amp;quot;&amp;gt;Other Projects&amp;lt;/h2&amp;gt;&lt;br /&gt;
    &amp;lt;div style=&amp;quot;clear: left&amp;quot;&amp;gt;&lt;br /&gt;
* [http://www.openlighting.org/libartnet-main/ libartnet]. The library that started it all, libartnet is an [[ArtNet]] implementation for Mac, Linux, Windows &amp;amp; iPhone.&lt;br /&gt;
* [[Logic RDM Sniffer]] - Use a [http://saleae.com/logic Saleae Logic] device as a RDM analyzer. &lt;br /&gt;
* [[Arduino RGB Mixer]], open source firmware for Arduinos, so that they can be used as a simple RGB Color Mixer. Now with RDM support!&lt;br /&gt;
* [[OLA_DMX_Trigger | DMX Trigger]], this can execute command line programs based on DMX values. It's useful for building DMX controlled media players.&lt;br /&gt;
* [[E1.33 SLP SA Tests]], similar to the RDM Responder Tests, this performs tests against a RDMNet Device's SLP implementation.&lt;br /&gt;
* [[OLA LED Pixels]], drive pixel strings using OLA&lt;br /&gt;
    &amp;lt;/div&amp;gt;&lt;br /&gt;
  &amp;lt;/td&amp;gt;&lt;br /&gt;
 &amp;lt;/tr&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td colspan=&amp;quot;2&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
 &amp;lt;tr&amp;gt;&lt;br /&gt;
  &amp;lt;td style=&amp;quot;width:45%; border:1px solid #cedff2; background:#f5faff; vertical-align:top; padding: 4px&amp;quot;&amp;gt;&lt;br /&gt;
    &amp;lt;h2 style=&amp;quot;float:left; font-size:120%; padding: .2em; margin:3px; font-weight:bold;&amp;quot;&amp;gt;Project Supporters&amp;lt;/h2&amp;gt;&lt;br /&gt;
    &amp;lt;div style=&amp;quot;clear: left&amp;quot;&amp;gt;Moved to the [http://www.openlighting.org/openlightingproject/supporters/ openlighting.org] site.&lt;br /&gt;
    &amp;lt;/div&amp;gt;&lt;br /&gt;
  &amp;lt;/td&amp;gt;&lt;br /&gt;
&lt;br /&gt;
  &amp;lt;td style=&amp;quot;width:45%; border:1px solid #cedff2; background:#f5faff; vertical-align:top; padding: 4px&amp;quot;&amp;gt;&lt;br /&gt;
    &amp;lt;h2 style=&amp;quot;float:left; font-size:120%; padding: .2em; margin:3px; font-weight:bold;&amp;quot;&amp;gt;Get Involved&amp;lt;/h2&amp;gt;&lt;br /&gt;
    &amp;lt;div style=&amp;quot;clear: left&amp;quot;&amp;gt;&lt;br /&gt;
There is plenty of opportunity to get involved. If you would like to help with any of the following (or have your own ideas) then please get in touch with us on the [http://groups.google.com/group/open-lighting Open Lighting Group]&lt;br /&gt;
&lt;br /&gt;
* Open Lighting participates in [[OLA SOC Ideas Page|Google Summer of Code]]&lt;br /&gt;
* Technical Writers, the documentation could do with some cleanup.&lt;br /&gt;
* Packagers, we need people to build binary packages for Mac, Debian/Ubuntu and RPM-based distros&lt;br /&gt;
* Windows programmers, are you interested in helping [[Building_OLA_for_Windows| port OLA to Windows]]?  &lt;br /&gt;
* Java programmers, we need someone to write the Java client API [https://github.com/OpenLightingProject/ola/issues/16]&lt;br /&gt;
* Equipment donation, do you own or know of a [[:Category:USB | USB interface]] or RDM device we don't support yet? Consider lending it to us.&lt;br /&gt;
* Web designers, the web UI could do with a facelift.&lt;br /&gt;
&lt;br /&gt;
    &amp;lt;/div&amp;gt;&lt;br /&gt;
  &amp;lt;/td&amp;gt;&lt;br /&gt;
 &amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;/table&amp;gt;&lt;br /&gt;
&lt;br /&gt;
__NOTOC__&lt;/div&gt;</summary>
		<author><name>Nightrune</name></author>	</entry>

	<entry>
		<id>https://wiki.openlighting.org/index.php?title=OLP_SOC_Ideas_Page&amp;diff=5664</id>
		<title>OLP SOC Ideas Page</title>
		<link rel="alternate" type="text/html" href="https://wiki.openlighting.org/index.php?title=OLP_SOC_Ideas_Page&amp;diff=5664"/>
				<updated>2014-02-24T19:01:35Z</updated>
		
		<summary type="html">&lt;p&gt;Nightrune: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This page lists some ideas for [http://www.google-melange.com/gsoc/homepage/google/gsoc2014 Google Summer of Code 2014] projects for the [[Open Lighting Project]]. You can use these ideas as a basis for your application, or come up with something different. Please see the Google SOC site for the 2014 timeline. If you would like to discuss any of these ideas, or are thinking of applying to work with us, please send an email to the [https://groups.google.com/forum/?fromgroups#!forum/open-lighting Open Lighting List] introducing yourself.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Please also see the [[GSOC Challenge]] page. You should complete this before applying.&lt;br /&gt;
&lt;br /&gt;
== Adding support for more RDM PIDS to the Web UI ==&lt;br /&gt;
&lt;br /&gt;
Our current WebUI lacks support for a lot of the really cool parameters and features that RDM is capable of. The main task of this project would to add support for RDM sub-devices and Ack Timer. &lt;br /&gt;
&lt;br /&gt;
This project would include:&lt;br /&gt;
* Adding support for RDM sub-devices in the UI and supporting code in the web server back-end &amp;lt;br/&amp;gt;&lt;br /&gt;
* Adding support for Ack Timer packets in the RDM flow &amp;lt;br/&amp;gt;&lt;br /&gt;
* Adding support for additional parameter ids or (PIDS).&lt;br /&gt;
'''Skills Required''': HTML, Javascript, C++ &amp;lt;br/&amp;gt;&lt;br /&gt;
'''Estimated Difficulty''': Medium&lt;br /&gt;
&lt;br /&gt;
== Raspberry Pi UI ==&lt;br /&gt;
&lt;br /&gt;
The Raspberry Pi is a great platform but lacks a good user interface. With the addition of a small touchscreen, a portable DMX/RDM debugger can be created.&lt;br /&gt;
&lt;br /&gt;
This project would include:&lt;br /&gt;
* Designing, writing and testing the new UI&lt;br /&gt;
&amp;lt;br/&amp;gt;&lt;br /&gt;
'''Skills Required''': Python ? &amp;lt;br/&amp;gt;&lt;br /&gt;
'''Estimated Difficulty''': Easy&lt;br /&gt;
&lt;br /&gt;
== RESTful API ==&lt;br /&gt;
&lt;br /&gt;
The current API that the website uses is a bit old and needs updated to allow full use of OLA's inner working in a general RESTful way. This would allow third parties to easily build new web based apps that could connect to RDM and DMX devices.&lt;br /&gt;
&lt;br /&gt;
This project would include:&lt;br /&gt;
* Writing and testing the new API&lt;br /&gt;
* Modifying our current Web app to use the new web api&lt;br /&gt;
&amp;lt;br/&amp;gt;&lt;br /&gt;
'''Skills Required''': C++, Javascript, HTML, JSON &amp;lt;br/&amp;gt;&lt;br /&gt;
'''Estimated Difficulty''': Easy&lt;br /&gt;
&lt;br /&gt;
== Web Based Configuration of Preferences ==&lt;br /&gt;
&lt;br /&gt;
User Preferences for [[OLA]] are stored in text files but the web UI provides no method for changing any preferences beyond port patchings. At the moment the user is required to stop the OLA Daemon, edit the text files and restart if settings are to be changed.  This project would involve building a generic preference store and exposing it through the web UI. Changing preferences on the fly is likely to expose bugs in some of the OLA plugins. These will need to be fixed.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Skills Required''': C++, Javascript, HTML   &amp;lt;br/&amp;gt;&lt;br /&gt;
'''Estimated Difficulty''': Easy&lt;br /&gt;
&lt;br /&gt;
== Asynchronous Web Notification of RDM Messages == &lt;br /&gt;
&lt;br /&gt;
Thanks to sites like GMail and Facebook, users have come to expect asynchronous notification of events in their web browser. [[RDM]] enabled lighting devices can generate events such as ''Over Temperature'' and ''Lamp Faulty'' so it would be nice to alert the users to this. This project would involve work with two Open Source efforts. The student would need to work with [http://www.gnu.org/software/libmicrohttpd/ libmicrohttpd] to add [http://en.wikipedia.org/wiki/WebSocket WebSocket] support (see the [http://lists.gnu.org/archive/html/libmicrohttpd/2012-01/msg00015.html email thread]).&lt;br /&gt;
&lt;br /&gt;
The second step would involve using WebSockets to deliver events to the browser, and building a UI to notify the user. The [[OLA]] UI is built with [http://code.google.com/closure/ Google Closure].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Skills Required''': C++, Network Programming, Javascript, HTML, Google Closure&amp;lt;br/&amp;gt;&lt;br /&gt;
'''Estimated Difficulty''': Medium&lt;br /&gt;
&lt;br /&gt;
==Port to Android==&lt;br /&gt;
&lt;br /&gt;
Android is an obvious target for [[OLA]]. Not only does it make perfect sense to use phones &amp;amp; tablets as lighting control interfaces but the Android platform could be used to build embedded lighting control devices. A small amount of this has been done, see [[OLA on Android]]. [https://github.com/OpenLightingProject/ola/issues/222 Bug #222] covers this work.&lt;br /&gt;
&lt;br /&gt;
This project would include:&lt;br /&gt;
* Building OLA as a Android Application&lt;br /&gt;
* Adding a [https://github.com/OpenLightingProject/ola/issues/16 Java client] or wrapping the C++ client with a Java library.&lt;br /&gt;
* Writing a frontend in Java to demonstrate the capabilities of OLA. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Skills Required''': C++, Java, Android &amp;lt;br/&amp;gt;&lt;br /&gt;
'''Estimated Difficulty''': Hard&lt;br /&gt;
&lt;br /&gt;
==Port to Windows ==&lt;br /&gt;
&lt;br /&gt;
This is the most requested 'feature' and would significantly expand the reach of the project especially as we approach v1.0. The current supported method of running OLA on Windows is using VMWare  ([[OLA_on_Windows_with_VMWare|instructions]]). This is sub optimal, since it requires the use of non-free software, is challenging for users without Unix command line experience, and doesn't allow Windows applications to communicate with OLA.  Work on a Windows port commenced in mid 2011 (see [[Building_OLA_for_Windows|these notes]]), but was postponed due to lack of resources.&lt;br /&gt;
&lt;br /&gt;
This project would include:&lt;br /&gt;
* Refactoring the base classes under [https://github.com/OpenLightingProject/ola/tree/master/common/network common/network] to use the Windows network &amp;amp; event management APIs and ensuring that all unit tests pass. &lt;br /&gt;
* Cleaning up various parts of the code which use POSIX APIs (see https://github.com/OpenLightingProject/ola/issues/140 for an example)&lt;br /&gt;
&lt;br /&gt;
A Windows port would enable lighting controller applications like [[QLC]] and [[D::Light]] to move to OLA entirely, and not have to maintain their own plugins.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''Skills Required''': C++, Windows Network Programming &amp;amp; Windows Event Handling&amp;lt;br/&amp;gt;&lt;br /&gt;
'''Estimated Difficulty''': Hard&lt;br /&gt;
&lt;br /&gt;
== Patcher v2 ==&lt;br /&gt;
&lt;br /&gt;
Patcher v2 is one of the next big projects for [[OLA]] it requires a rewrite of our current daemon to allow users to patch a specific channel:universe to a different channel:universe. It would most likely not be entirely up to the student but would be a small team effort as this touches all major points of our system. This would also require a change in the web interface to possibly allow drag and drop of patching. Depending on the students knowledge they may help with the web interface, web backend or the OLA daemon.&lt;br /&gt;
&lt;br /&gt;
See https://github.com/OpenLightingProject/ola/issues/280 for some additional features and thoughts.&lt;br /&gt;
&lt;br /&gt;
'''Skills Required''': C++, Javascript, HTML   &amp;lt;br/&amp;gt;&lt;br /&gt;
'''Estimated Difficulty''': Hard&lt;/div&gt;</summary>
		<author><name>Nightrune</name></author>	</entry>

	<entry>
		<id>https://wiki.openlighting.org/index.php?title=OLP_SOC_Ideas_Page&amp;diff=5663</id>
		<title>OLP SOC Ideas Page</title>
		<link rel="alternate" type="text/html" href="https://wiki.openlighting.org/index.php?title=OLP_SOC_Ideas_Page&amp;diff=5663"/>
				<updated>2014-02-24T18:55:16Z</updated>
		
		<summary type="html">&lt;p&gt;Nightrune: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This page lists some ideas for [http://www.google-melange.com/gsoc/homepage/google/gsoc2014 Google Summer of Code 2014] projects for the [[Open Lighting Project]]. You can use these ideas as a basis for your application, or come up with something different. Please see the Google SOC site for the 2014 timeline. If you would like to discuss any of these ideas, or are thinking of applying to work with us, please send an email to the [https://groups.google.com/forum/?fromgroups#!forum/open-lighting Open Lighting List] introducing yourself.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Please also see the [[GSOC Challenge]] page. You should complete this before applying.&lt;br /&gt;
&lt;br /&gt;
== Adding support for more RDM PIDS to the Web UI ==&lt;br /&gt;
&lt;br /&gt;
Our current WebUI lacks support for a lot of the really cool parameters and features that RDM is capable of. The main task of this project would to add support for RDM Sub devices then and ack timer. &lt;br /&gt;
&lt;br /&gt;
This project would include:&lt;br /&gt;
* Adding support for RDM sub-devices in the UI and supporting code in the web server back-end &amp;lt;br/&amp;gt;&lt;br /&gt;
* Adding support for Ack Timer packets in the RDM flow &amp;lt;br/&amp;gt;&lt;br /&gt;
* Adding support for additional parameter ids or (PIDS).&lt;br /&gt;
'''Skills Required''': HTML, Javascript, C++ &amp;lt;br/&amp;gt;&lt;br /&gt;
'''Estimated Difficulty''': Medium&lt;br /&gt;
&lt;br /&gt;
== Raspberry Pi UI ==&lt;br /&gt;
&lt;br /&gt;
The Raspberry Pi is a great platform but lacks a good user interface. With the addition of a small touchscreen, a portable DMX/RDM debugger can be created.&lt;br /&gt;
&lt;br /&gt;
This project would include:&lt;br /&gt;
* Designing, writing and testing the new UI&lt;br /&gt;
&amp;lt;br/&amp;gt;&lt;br /&gt;
'''Skills Required''': Python ? &amp;lt;br/&amp;gt;&lt;br /&gt;
'''Estimated Difficulty''': Easy&lt;br /&gt;
&lt;br /&gt;
== RESTful API ==&lt;br /&gt;
&lt;br /&gt;
The current API that the website uses is a bit old and needs updated to allow full use of OLA's inner working in a general RESTful way. This would allow third parties to easily build new web based apps that could connect to RDM and DMX devices.&lt;br /&gt;
&lt;br /&gt;
This project would include:&lt;br /&gt;
* Writing and testing the new API&lt;br /&gt;
* Modifying our current Web app to use the new web api&lt;br /&gt;
&amp;lt;br/&amp;gt;&lt;br /&gt;
'''Skills Required''': C++, Javascript, HTML, JSON &amp;lt;br/&amp;gt;&lt;br /&gt;
'''Estimated Difficulty''': Easy&lt;br /&gt;
&lt;br /&gt;
== Web Based Configuration of Preferences ==&lt;br /&gt;
&lt;br /&gt;
User Preferences for [[OLA]] are stored in text files but the web UI provides no method for changing any preferences beyond port patchings. At the moment the user is required to stop the OLA Daemon, edit the text files and restart if settings are to be changed.  This project would involve building a generic preference store and exposing it through the web UI. Changing preferences on the fly is likely to expose bugs in some of the OLA plugins. These will need to be fixed.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Skills Required''': C++, Javascript, HTML   &amp;lt;br/&amp;gt;&lt;br /&gt;
'''Estimated Difficulty''': Easy&lt;br /&gt;
&lt;br /&gt;
== Asynchronous Web Notification of RDM Messages == &lt;br /&gt;
&lt;br /&gt;
Thanks to sites like GMail and Facebook, users have come to expect asynchronous notification of events in their web browser. [[RDM]] enabled lighting devices can generate events such as ''Over Temperature'' and ''Lamp Faulty'' so it would be nice to alert the users to this. This project would involve work with two Open Source efforts. The student would need to work with [http://www.gnu.org/software/libmicrohttpd/ libmicrohttpd] to add [http://en.wikipedia.org/wiki/WebSocket WebSocket] support (see the [http://lists.gnu.org/archive/html/libmicrohttpd/2012-01/msg00015.html email thread]).&lt;br /&gt;
&lt;br /&gt;
The second step would involve using WebSockets to deliver events to the browser, and building a UI to notify the user. The [[OLA]] UI is built with [http://code.google.com/closure/ Google Closure].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Skills Required''': C++, Network Programming, Javascript, HTML, Google Closure&amp;lt;br/&amp;gt;&lt;br /&gt;
'''Estimated Difficulty''': Medium&lt;br /&gt;
&lt;br /&gt;
==Port to Android==&lt;br /&gt;
&lt;br /&gt;
Android is an obvious target for [[OLA]]. Not only does it make perfect sense to use phones &amp;amp; tablets as lighting control interfaces but the Android platform could be used to build embedded lighting control devices. A small amount of this has been done, see [[OLA on Android]]. [https://github.com/OpenLightingProject/ola/issues/222 Bug #222] covers this work.&lt;br /&gt;
&lt;br /&gt;
This project would include:&lt;br /&gt;
* Building OLA as a Android Application&lt;br /&gt;
* Adding a [https://github.com/OpenLightingProject/ola/issues/16 Java client] or wrapping the C++ client with a Java library.&lt;br /&gt;
* Writing a frontend in Java to demonstrate the capabilities of OLA. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Skills Required''': C++, Java, Android &amp;lt;br/&amp;gt;&lt;br /&gt;
'''Estimated Difficulty''': Hard&lt;br /&gt;
&lt;br /&gt;
==Port to Windows ==&lt;br /&gt;
&lt;br /&gt;
This is the most requested 'feature' and would significantly expand the reach of the project especially as we approach v1.0. The current supported method of running OLA on Windows is using VMWare  ([[OLA_on_Windows_with_VMWare|instructions]]). This is sub optimal, since it requires the use of non-free software, is challenging for users without Unix command line experience, and doesn't allow Windows applications to communicate with OLA.  Work on a Windows port commenced in mid 2011 (see [[Building_OLA_for_Windows|these notes]]), but was postponed due to lack of resources.&lt;br /&gt;
&lt;br /&gt;
This project would include:&lt;br /&gt;
* Refactoring the base classes under [https://github.com/OpenLightingProject/ola/tree/master/common/network common/network] to use the Windows network &amp;amp; event management APIs and ensuring that all unit tests pass. &lt;br /&gt;
* Cleaning up various parts of the code which use POSIX APIs (see https://github.com/OpenLightingProject/ola/issues/140 for an example)&lt;br /&gt;
&lt;br /&gt;
A Windows port would enable lighting controller applications like [[QLC]] and [[D::Light]] to move to OLA entirely, and not have to maintain their own plugins.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''Skills Required''': C++, Windows Network Programming &amp;amp; Windows Event Handling&amp;lt;br/&amp;gt;&lt;br /&gt;
'''Estimated Difficulty''': Hard&lt;br /&gt;
&lt;br /&gt;
== Patcher v2 ==&lt;br /&gt;
&lt;br /&gt;
Patcher v2 is one of the next big projects for [[OLA]] it requires a rewrite of our current daemon to allow users to patch a specific channel:universe to a different channel:universe. It would most likely not be entirely up to the student but would be a small team effort as this touches all major points of our system. This would also require a change in the web interface to possibly allow drag and drop of patching. Depending on the students knowledge they may help with the web interface, web backend or the OLA daemon.&lt;br /&gt;
&lt;br /&gt;
See https://github.com/OpenLightingProject/ola/issues/280 for some additional features and thoughts.&lt;br /&gt;
&lt;br /&gt;
'''Skills Required''': C++, Javascript, HTML   &amp;lt;br/&amp;gt;&lt;br /&gt;
'''Estimated Difficulty''': Hard&lt;/div&gt;</summary>
		<author><name>Nightrune</name></author>	</entry>

	<entry>
		<id>https://wiki.openlighting.org/index.php?title=OLP_SOC_Ideas_Page&amp;diff=5653</id>
		<title>OLP SOC Ideas Page</title>
		<link rel="alternate" type="text/html" href="https://wiki.openlighting.org/index.php?title=OLP_SOC_Ideas_Page&amp;diff=5653"/>
				<updated>2014-02-13T16:47:33Z</updated>
		
		<summary type="html">&lt;p&gt;Nightrune: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This page lists some ideas for [http://www.google-melange.com/gsoc/homepage/google/gsoc2014 Google Summer of Code 2014] projects for the [[Open Lighting Project]]. You can use these ideas as a basis for your application, or come up with something different. Please see the Google SOC site for the 2014 timeline. If you would like to discuss any of these ideas, or are thinking of applying to work with us, please send an email to the [https://groups.google.com/forum/?fromgroups#!forum/open-lighting Open Lighting List] introducing yourself.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Please also see the [[GSOC Challenge]] page. You should complete this before applying.&lt;br /&gt;
&lt;br /&gt;
== RESTful API ==&lt;br /&gt;
&lt;br /&gt;
The current API that the website uses is a bit old and needs updated to allow full use of OLA's inner working in a general RESTful way. This would allow third parties to easily build new web based apps that could connect to RDM and DMX devices.&lt;br /&gt;
&lt;br /&gt;
This project would include:&lt;br /&gt;
* Writing and testing the new API&lt;br /&gt;
* Modifying our current Web app to use the new web api&lt;br /&gt;
&amp;lt;br/&amp;gt;&lt;br /&gt;
'''Skills Required''': C++, Javascript, HTML, JSON &amp;lt;br/&amp;gt;&lt;br /&gt;
'''Estimated Difficulty''': Easy&lt;br /&gt;
&lt;br /&gt;
== Web Based Configuration of Preferences ==&lt;br /&gt;
&lt;br /&gt;
User Preferences for [[OLA]] are stored in text files but the web UI provides no method for changing any preferences beyond port patchings. At the moment the user is required to stop the OLA Daemon, exit the text files and restart if settings are to be changed.  This project would involve building a generic preference store and exposing it through the web UI. Changing preferences on the fly is likely to expose bugs in some of the OLA plugins. These will need to be fixed.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Skills Required''': C++, Javascript, HTML   &amp;lt;br/&amp;gt;&lt;br /&gt;
'''Estimated Difficulty''': Easy&lt;br /&gt;
&lt;br /&gt;
== Asynchronous Web Notification of RDM Messages == &lt;br /&gt;
&lt;br /&gt;
Thanks to sites like GMail and Facebook, users have come to expect asynchronous notification of events in their web browser. [[RDM]] enabled lighting devices can generate events such as ''Over Temperature'' and ''Lamp Faulty'' so it would be nice to alert the users to this. This project would involve work with two Open Source efforts. The student would need to work with [http://www.gnu.org/software/libmicrohttpd/ libmicrohttpd] to add [http://en.wikipedia.org/wiki/WebSocket WebSocket] support (see the [http://lists.gnu.org/archive/html/libmicrohttpd/2012-01/msg00015.html email thread]).&lt;br /&gt;
&lt;br /&gt;
The second step would involve using WebSockets to deliver events to the browser, and building a UI to notify the user. The [[OLA]] UI is built with [http://code.google.com/closure/ Google Closure].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Skills Required''': C++, Network Programming, Javascript, HTML, Google Closure&amp;lt;br/&amp;gt;&lt;br /&gt;
'''Estimated Difficulty''': Medium&lt;br /&gt;
&lt;br /&gt;
==Port to Android==&lt;br /&gt;
&lt;br /&gt;
Android is an obvious target for [[OLA]]. Not only does it make perfect sense to use phones &amp;amp; tablets as lighting control interfaces but the Android platform could be used to build embedded lighting control devices. A small amount of this has been done, see [[OLA on Android]]. [https://code.google.com/p/open-lighting/issues/detail?id=221 Bug #221] covers this work.&lt;br /&gt;
&lt;br /&gt;
This project would include:&lt;br /&gt;
* Building OLA as a Android Application&lt;br /&gt;
* Adding a [http://code.google.com/p/linux-lighting/issues/detail?id=15&amp;amp;colspec=ID%20Type%20Status%20Priority%20Component%20Milestone%20Summary Java client] or wrapping the C++ client with a Java library.&lt;br /&gt;
* Writing a frontend in Java to demonstrate the capabilities of OLA. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Skills Required''': C++, Java, Android &amp;lt;br/&amp;gt;&lt;br /&gt;
'''Estimated Difficulty''': Hard&lt;br /&gt;
&lt;br /&gt;
==Port to Windows ==&lt;br /&gt;
&lt;br /&gt;
This is the most requested 'feature' and would significantly expand the reach of the project especially as we approach v1.0. The current supported method of running OLA on Windows is using VMWare  ([[OLA_on_Windows_with_VMWare|instructions]]). This is sub optimal, since it requires the use of non-free software, is challenging for users without unix command line experience, and doesn't allow Windows applications to communicate with OLA.  Work on a Windows port commenced in mid 2011 (see [[Building_OLA_for_Windows|these Notes]]), but was postponed due to lack of resources.&lt;br /&gt;
&lt;br /&gt;
This project would include:&lt;br /&gt;
* Refactoring the base classes under [http://code.google.com/p/linux-lighting/source/browse/#git%2Fcommon%2Fnetwork common/network] to use the Windows network &amp;amp; event management APIs and ensuring that all unit tests pass. &lt;br /&gt;
* Cleaning up various parts of the code which use POSIX APIs (see http://code.google.com/p/linux-lighting/issues/detail?id=139 for an example)&lt;br /&gt;
&lt;br /&gt;
A Windows port would enable lighting controller applications like [[QLC]] and [[D::Light]] to move to OLA entirely, and not have to maintain their own plugins.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''Skills Required''': C++, Windows Network Programming &amp;amp; Windows Event Handling&amp;lt;br/&amp;gt;&lt;br /&gt;
'''Estimated Difficulty''': Hard&lt;br /&gt;
&lt;br /&gt;
== Patcher v2 ==&lt;br /&gt;
&lt;br /&gt;
Patcher v2 is one of the next big projects for [[OLA]] it requires a rewrite of our current daemon to allow users to patch a specific channel:universe to a different channel:universe. It would most likely not be entirely up to the student but would be a small team effort as this touches all major points of our system. This would also require a change in the web interface to possibly allow drag and drop of patching. Depending on the students knowledge they may help with the web interface, web backend or the OLA daemon.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Skills Required''': C++, Javascript, HTML   &amp;lt;br/&amp;gt;&lt;br /&gt;
'''Estimated Difficulty''': Hard&lt;/div&gt;</summary>
		<author><name>Nightrune</name></author>	</entry>

	<entry>
		<id>https://wiki.openlighting.org/index.php?title=OLP_SOC_Ideas_Page&amp;diff=5652</id>
		<title>OLP SOC Ideas Page</title>
		<link rel="alternate" type="text/html" href="https://wiki.openlighting.org/index.php?title=OLP_SOC_Ideas_Page&amp;diff=5652"/>
				<updated>2014-02-13T16:43:39Z</updated>
		
		<summary type="html">&lt;p&gt;Nightrune: /* Patcher v2 */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This page lists some ideas for [http://www.google-melange.com/gsoc/homepage/google/gsoc2014 Google Summer of Code 2014] projects for the [[Open Lighting Project]]. You can use these ideas as a basis for your application, or come up with something different. Please see the Google SOC site for the 2014 timeline. If you would like to discuss any of these ideas, or are thinking of applying to work with us, please send an email to the [https://groups.google.com/forum/?fromgroups#!forum/open-lighting Open Lighting List] introducing yourself.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Please also see the [[GSOC Challenge]] page. You should complete this before applying.&lt;br /&gt;
&lt;br /&gt;
== RESTful API ==&lt;br /&gt;
&lt;br /&gt;
The current API that the website uses is a bit old and needs updated to allow full use of OLA's inner working in a general RESTful way. This would allow third parties to easily build new web based apps that could connect to RDM and DMX devices.&lt;br /&gt;
&lt;br /&gt;
This project would include:&lt;br /&gt;
* Writing and testing the new API&lt;br /&gt;
* Modifying our current Web app to use the new web api&lt;br /&gt;
&amp;lt;br/&amp;gt;&lt;br /&gt;
'''Skills Required''': C++, Javascript, HTML, JSON &amp;lt;br/&amp;gt;&lt;br /&gt;
'''Estimated Difficulty''': Easy&lt;br /&gt;
&lt;br /&gt;
==Port to Android==&lt;br /&gt;
&lt;br /&gt;
Android is an obvious target for [[OLA]]. Not only does it make perfect sense to use phones &amp;amp; tablets as lighting control interfaces but the Android platform could be used to build embedded lighting control devices. A small amount of this has been done, see [[OLA on Android]]. [https://code.google.com/p/open-lighting/issues/detail?id=221 Bug #221] covers this work.&lt;br /&gt;
&lt;br /&gt;
This project would include:&lt;br /&gt;
* Building OLA as a Android Application&lt;br /&gt;
* Adding a [http://code.google.com/p/linux-lighting/issues/detail?id=15&amp;amp;colspec=ID%20Type%20Status%20Priority%20Component%20Milestone%20Summary Java client] or wrapping the C++ client with a Java library.&lt;br /&gt;
* Writing a frontend in Java to demonstrate the capabilities of OLA. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Skills Required''': C++, Java, Android &amp;lt;br/&amp;gt;&lt;br /&gt;
'''Estimated Difficulty''': Hard&lt;br /&gt;
&lt;br /&gt;
==Port to Windows ==&lt;br /&gt;
&lt;br /&gt;
This is the most requested 'feature' and would significantly expand the reach of the project especially as we approach v1.0. The current supported method of running OLA on Windows is using VMWare  ([[OLA_on_Windows_with_VMWare|instructions]]). This is sub optimal, since it requires the use of non-free software, is challenging for users without unix command line experience, and doesn't allow Windows applications to communicate with OLA.  Work on a Windows port commenced in mid 2011 (see [[Building_OLA_for_Windows|these Notes]]), but was postponed due to lack of resources.&lt;br /&gt;
&lt;br /&gt;
This project would include:&lt;br /&gt;
* Refactoring the base classes under [http://code.google.com/p/linux-lighting/source/browse/#git%2Fcommon%2Fnetwork common/network] to use the Windows network &amp;amp; event management APIs and ensuring that all unit tests pass. &lt;br /&gt;
* Cleaning up various parts of the code which use POSIX APIs (see http://code.google.com/p/linux-lighting/issues/detail?id=139 for an example)&lt;br /&gt;
&lt;br /&gt;
A Windows port would enable lighting controller applications like [[QLC]] and [[D::Light]] to move to OLA entirely, and not have to maintain their own plugins.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''Skills Required''': C++, Windows Network Programming &amp;amp; Windows Event Handling&amp;lt;br/&amp;gt;&lt;br /&gt;
'''Estimated Difficulty''': Hard&lt;br /&gt;
&lt;br /&gt;
== Asynchronous Web Notification of RDM Messages == &lt;br /&gt;
&lt;br /&gt;
Thanks to sites like GMail and Facebook, users have come to expect asynchronous notification of events in their web browser. [[RDM]] enabled lighting devices can generate events such as ''Over Temperature'' and ''Lamp Faulty'' so it would be nice to alert the users to this. This project would involve work with two Open Source efforts. The student would need to work with [http://www.gnu.org/software/libmicrohttpd/ libmicrohttpd] to add [http://en.wikipedia.org/wiki/WebSocket WebSocket] support (see the [http://lists.gnu.org/archive/html/libmicrohttpd/2012-01/msg00015.html email thread]).&lt;br /&gt;
&lt;br /&gt;
The second step would involve using WebSockets to deliver events to the browser, and building a UI to notify the user. The [[OLA]] UI is built with [http://code.google.com/closure/ Google Closure].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Skills Required''': C++, Network Programming, Javascript, HTML, Google Closure&amp;lt;br/&amp;gt;&lt;br /&gt;
'''Estimated Difficulty''': Medium&lt;br /&gt;
&lt;br /&gt;
== Web Based Configuration of Preferences ==&lt;br /&gt;
&lt;br /&gt;
User Preferences for [[OLA]] are stored in text files but the web UI provides no method for changing any preferences beyond port patchings. At the moment the user is required to stop the OLA Daemon, exit the text files and restart if settings are to be changed.  This project would involve building a generic preference store and exposing it through the web UI. Changing preferences on the fly is likely to expose bugs in some of the OLA plugins. These will need to be fixed.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Skills Required''': C++, Javascript, HTML   &amp;lt;br/&amp;gt;&lt;br /&gt;
'''Estimated Difficulty''': Easy&lt;br /&gt;
&lt;br /&gt;
== Patcher v2 ==&lt;br /&gt;
&lt;br /&gt;
Patcher v2 is one of the next big projects for [[OLA]] it requires a rewrite of our current daemon to allow users to patch a specific channel:universe to a different channel:universe. It would most likely not be entirely up to the student but would be a small team effort as this touches all major points of our system. This would also require a change in the web interface to possibly allow drag and drop of patching. Depending on the students knowledge they may help with the web interface, web backend or the OLA daemon.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Skills Required''': C++, Javascript, HTML   &amp;lt;br/&amp;gt;&lt;br /&gt;
'''Estimated Difficulty''': Hard&lt;/div&gt;</summary>
		<author><name>Nightrune</name></author>	</entry>

	<entry>
		<id>https://wiki.openlighting.org/index.php?title=OLP_SOC_Ideas_Page&amp;diff=5651</id>
		<title>OLP SOC Ideas Page</title>
		<link rel="alternate" type="text/html" href="https://wiki.openlighting.org/index.php?title=OLP_SOC_Ideas_Page&amp;diff=5651"/>
				<updated>2014-02-13T16:43:26Z</updated>
		
		<summary type="html">&lt;p&gt;Nightrune: /* Web Based Configuration of Preferences */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This page lists some ideas for [http://www.google-melange.com/gsoc/homepage/google/gsoc2014 Google Summer of Code 2014] projects for the [[Open Lighting Project]]. You can use these ideas as a basis for your application, or come up with something different. Please see the Google SOC site for the 2014 timeline. If you would like to discuss any of these ideas, or are thinking of applying to work with us, please send an email to the [https://groups.google.com/forum/?fromgroups#!forum/open-lighting Open Lighting List] introducing yourself.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Please also see the [[GSOC Challenge]] page. You should complete this before applying.&lt;br /&gt;
&lt;br /&gt;
== RESTful API ==&lt;br /&gt;
&lt;br /&gt;
The current API that the website uses is a bit old and needs updated to allow full use of OLA's inner working in a general RESTful way. This would allow third parties to easily build new web based apps that could connect to RDM and DMX devices.&lt;br /&gt;
&lt;br /&gt;
This project would include:&lt;br /&gt;
* Writing and testing the new API&lt;br /&gt;
* Modifying our current Web app to use the new web api&lt;br /&gt;
&amp;lt;br/&amp;gt;&lt;br /&gt;
'''Skills Required''': C++, Javascript, HTML, JSON &amp;lt;br/&amp;gt;&lt;br /&gt;
'''Estimated Difficulty''': Easy&lt;br /&gt;
&lt;br /&gt;
==Port to Android==&lt;br /&gt;
&lt;br /&gt;
Android is an obvious target for [[OLA]]. Not only does it make perfect sense to use phones &amp;amp; tablets as lighting control interfaces but the Android platform could be used to build embedded lighting control devices. A small amount of this has been done, see [[OLA on Android]]. [https://code.google.com/p/open-lighting/issues/detail?id=221 Bug #221] covers this work.&lt;br /&gt;
&lt;br /&gt;
This project would include:&lt;br /&gt;
* Building OLA as a Android Application&lt;br /&gt;
* Adding a [http://code.google.com/p/linux-lighting/issues/detail?id=15&amp;amp;colspec=ID%20Type%20Status%20Priority%20Component%20Milestone%20Summary Java client] or wrapping the C++ client with a Java library.&lt;br /&gt;
* Writing a frontend in Java to demonstrate the capabilities of OLA. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Skills Required''': C++, Java, Android &amp;lt;br/&amp;gt;&lt;br /&gt;
'''Estimated Difficulty''': Hard&lt;br /&gt;
&lt;br /&gt;
==Port to Windows ==&lt;br /&gt;
&lt;br /&gt;
This is the most requested 'feature' and would significantly expand the reach of the project especially as we approach v1.0. The current supported method of running OLA on Windows is using VMWare  ([[OLA_on_Windows_with_VMWare|instructions]]). This is sub optimal, since it requires the use of non-free software, is challenging for users without unix command line experience, and doesn't allow Windows applications to communicate with OLA.  Work on a Windows port commenced in mid 2011 (see [[Building_OLA_for_Windows|these Notes]]), but was postponed due to lack of resources.&lt;br /&gt;
&lt;br /&gt;
This project would include:&lt;br /&gt;
* Refactoring the base classes under [http://code.google.com/p/linux-lighting/source/browse/#git%2Fcommon%2Fnetwork common/network] to use the Windows network &amp;amp; event management APIs and ensuring that all unit tests pass. &lt;br /&gt;
* Cleaning up various parts of the code which use POSIX APIs (see http://code.google.com/p/linux-lighting/issues/detail?id=139 for an example)&lt;br /&gt;
&lt;br /&gt;
A Windows port would enable lighting controller applications like [[QLC]] and [[D::Light]] to move to OLA entirely, and not have to maintain their own plugins.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''Skills Required''': C++, Windows Network Programming &amp;amp; Windows Event Handling&amp;lt;br/&amp;gt;&lt;br /&gt;
'''Estimated Difficulty''': Hard&lt;br /&gt;
&lt;br /&gt;
== Asynchronous Web Notification of RDM Messages == &lt;br /&gt;
&lt;br /&gt;
Thanks to sites like GMail and Facebook, users have come to expect asynchronous notification of events in their web browser. [[RDM]] enabled lighting devices can generate events such as ''Over Temperature'' and ''Lamp Faulty'' so it would be nice to alert the users to this. This project would involve work with two Open Source efforts. The student would need to work with [http://www.gnu.org/software/libmicrohttpd/ libmicrohttpd] to add [http://en.wikipedia.org/wiki/WebSocket WebSocket] support (see the [http://lists.gnu.org/archive/html/libmicrohttpd/2012-01/msg00015.html email thread]).&lt;br /&gt;
&lt;br /&gt;
The second step would involve using WebSockets to deliver events to the browser, and building a UI to notify the user. The [[OLA]] UI is built with [http://code.google.com/closure/ Google Closure].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Skills Required''': C++, Network Programming, Javascript, HTML, Google Closure&amp;lt;br/&amp;gt;&lt;br /&gt;
'''Estimated Difficulty''': Medium&lt;br /&gt;
&lt;br /&gt;
== Web Based Configuration of Preferences ==&lt;br /&gt;
&lt;br /&gt;
User Preferences for [[OLA]] are stored in text files but the web UI provides no method for changing any preferences beyond port patchings. At the moment the user is required to stop the OLA Daemon, exit the text files and restart if settings are to be changed.  This project would involve building a generic preference store and exposing it through the web UI. Changing preferences on the fly is likely to expose bugs in some of the OLA plugins. These will need to be fixed.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Skills Required''': C++, Javascript, HTML   &amp;lt;br/&amp;gt;&lt;br /&gt;
'''Estimated Difficulty''': Easy&lt;br /&gt;
&lt;br /&gt;
== Patcher v2 ==&lt;br /&gt;
&lt;br /&gt;
Patcher v2 is one of the next big projects for [[OLA]] it requires a rewrite of our current daemon to allow users to patch a specific channel:universe to a different channel:universe. It would most likely not be entirely up to the student but would be a small team effort as this touches all major points of our system. This would also require a change in the web interface to possibly allow drag and drop of patching. Depending on the students knowledge they may help with the web interface, web backend or the OLA daemon.&lt;br /&gt;
&lt;br /&gt;
'''Skills Required''': C++, Javascript, HTML   &amp;lt;br/&amp;gt;&lt;br /&gt;
'''Estimated Difficulty''': Hard&lt;/div&gt;</summary>
		<author><name>Nightrune</name></author>	</entry>

	<entry>
		<id>https://wiki.openlighting.org/index.php?title=OLP_SOC_Ideas_Page&amp;diff=5650</id>
		<title>OLP SOC Ideas Page</title>
		<link rel="alternate" type="text/html" href="https://wiki.openlighting.org/index.php?title=OLP_SOC_Ideas_Page&amp;diff=5650"/>
				<updated>2014-02-13T16:43:14Z</updated>
		
		<summary type="html">&lt;p&gt;Nightrune: /* Asynchronous Web Notification of RDM Messages */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This page lists some ideas for [http://www.google-melange.com/gsoc/homepage/google/gsoc2014 Google Summer of Code 2014] projects for the [[Open Lighting Project]]. You can use these ideas as a basis for your application, or come up with something different. Please see the Google SOC site for the 2014 timeline. If you would like to discuss any of these ideas, or are thinking of applying to work with us, please send an email to the [https://groups.google.com/forum/?fromgroups#!forum/open-lighting Open Lighting List] introducing yourself.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Please also see the [[GSOC Challenge]] page. You should complete this before applying.&lt;br /&gt;
&lt;br /&gt;
== RESTful API ==&lt;br /&gt;
&lt;br /&gt;
The current API that the website uses is a bit old and needs updated to allow full use of OLA's inner working in a general RESTful way. This would allow third parties to easily build new web based apps that could connect to RDM and DMX devices.&lt;br /&gt;
&lt;br /&gt;
This project would include:&lt;br /&gt;
* Writing and testing the new API&lt;br /&gt;
* Modifying our current Web app to use the new web api&lt;br /&gt;
&amp;lt;br/&amp;gt;&lt;br /&gt;
'''Skills Required''': C++, Javascript, HTML, JSON &amp;lt;br/&amp;gt;&lt;br /&gt;
'''Estimated Difficulty''': Easy&lt;br /&gt;
&lt;br /&gt;
==Port to Android==&lt;br /&gt;
&lt;br /&gt;
Android is an obvious target for [[OLA]]. Not only does it make perfect sense to use phones &amp;amp; tablets as lighting control interfaces but the Android platform could be used to build embedded lighting control devices. A small amount of this has been done, see [[OLA on Android]]. [https://code.google.com/p/open-lighting/issues/detail?id=221 Bug #221] covers this work.&lt;br /&gt;
&lt;br /&gt;
This project would include:&lt;br /&gt;
* Building OLA as a Android Application&lt;br /&gt;
* Adding a [http://code.google.com/p/linux-lighting/issues/detail?id=15&amp;amp;colspec=ID%20Type%20Status%20Priority%20Component%20Milestone%20Summary Java client] or wrapping the C++ client with a Java library.&lt;br /&gt;
* Writing a frontend in Java to demonstrate the capabilities of OLA. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Skills Required''': C++, Java, Android &amp;lt;br/&amp;gt;&lt;br /&gt;
'''Estimated Difficulty''': Hard&lt;br /&gt;
&lt;br /&gt;
==Port to Windows ==&lt;br /&gt;
&lt;br /&gt;
This is the most requested 'feature' and would significantly expand the reach of the project especially as we approach v1.0. The current supported method of running OLA on Windows is using VMWare  ([[OLA_on_Windows_with_VMWare|instructions]]). This is sub optimal, since it requires the use of non-free software, is challenging for users without unix command line experience, and doesn't allow Windows applications to communicate with OLA.  Work on a Windows port commenced in mid 2011 (see [[Building_OLA_for_Windows|these Notes]]), but was postponed due to lack of resources.&lt;br /&gt;
&lt;br /&gt;
This project would include:&lt;br /&gt;
* Refactoring the base classes under [http://code.google.com/p/linux-lighting/source/browse/#git%2Fcommon%2Fnetwork common/network] to use the Windows network &amp;amp; event management APIs and ensuring that all unit tests pass. &lt;br /&gt;
* Cleaning up various parts of the code which use POSIX APIs (see http://code.google.com/p/linux-lighting/issues/detail?id=139 for an example)&lt;br /&gt;
&lt;br /&gt;
A Windows port would enable lighting controller applications like [[QLC]] and [[D::Light]] to move to OLA entirely, and not have to maintain their own plugins.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''Skills Required''': C++, Windows Network Programming &amp;amp; Windows Event Handling&amp;lt;br/&amp;gt;&lt;br /&gt;
'''Estimated Difficulty''': Hard&lt;br /&gt;
&lt;br /&gt;
== Asynchronous Web Notification of RDM Messages == &lt;br /&gt;
&lt;br /&gt;
Thanks to sites like GMail and Facebook, users have come to expect asynchronous notification of events in their web browser. [[RDM]] enabled lighting devices can generate events such as ''Over Temperature'' and ''Lamp Faulty'' so it would be nice to alert the users to this. This project would involve work with two Open Source efforts. The student would need to work with [http://www.gnu.org/software/libmicrohttpd/ libmicrohttpd] to add [http://en.wikipedia.org/wiki/WebSocket WebSocket] support (see the [http://lists.gnu.org/archive/html/libmicrohttpd/2012-01/msg00015.html email thread]).&lt;br /&gt;
&lt;br /&gt;
The second step would involve using WebSockets to deliver events to the browser, and building a UI to notify the user. The [[OLA]] UI is built with [http://code.google.com/closure/ Google Closure].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Skills Required''': C++, Network Programming, Javascript, HTML, Google Closure&amp;lt;br/&amp;gt;&lt;br /&gt;
'''Estimated Difficulty''': Medium&lt;br /&gt;
&lt;br /&gt;
== Web Based Configuration of Preferences ==&lt;br /&gt;
&lt;br /&gt;
User Preferences for [[OLA]] are stored in text files but the web UI provides no method for changing any preferences beyond port patchings. At the moment the user is required to stop the OLA Daemon, exit the text files and restart if settings are to be changed.  This project would involve building a generic preference store and exposing it through the web UI. Changing preferences on the fly is likely to expose bugs in some of the OLA plugins. These will need to be fixed.&lt;br /&gt;
&lt;br /&gt;
'''Skills Required''': C++, Javascript, HTML   &amp;lt;br/&amp;gt;&lt;br /&gt;
'''Estimated Difficulty''': Easy&lt;br /&gt;
&lt;br /&gt;
== Patcher v2 ==&lt;br /&gt;
&lt;br /&gt;
Patcher v2 is one of the next big projects for [[OLA]] it requires a rewrite of our current daemon to allow users to patch a specific channel:universe to a different channel:universe. It would most likely not be entirely up to the student but would be a small team effort as this touches all major points of our system. This would also require a change in the web interface to possibly allow drag and drop of patching. Depending on the students knowledge they may help with the web interface, web backend or the OLA daemon.&lt;br /&gt;
&lt;br /&gt;
'''Skills Required''': C++, Javascript, HTML   &amp;lt;br/&amp;gt;&lt;br /&gt;
'''Estimated Difficulty''': Hard&lt;/div&gt;</summary>
		<author><name>Nightrune</name></author>	</entry>

	<entry>
		<id>https://wiki.openlighting.org/index.php?title=OLP_SOC_Ideas_Page&amp;diff=5649</id>
		<title>OLP SOC Ideas Page</title>
		<link rel="alternate" type="text/html" href="https://wiki.openlighting.org/index.php?title=OLP_SOC_Ideas_Page&amp;diff=5649"/>
				<updated>2014-02-13T16:42:58Z</updated>
		
		<summary type="html">&lt;p&gt;Nightrune: /* Asynchronous Web Notification of RDM Messages */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This page lists some ideas for [http://www.google-melange.com/gsoc/homepage/google/gsoc2014 Google Summer of Code 2014] projects for the [[Open Lighting Project]]. You can use these ideas as a basis for your application, or come up with something different. Please see the Google SOC site for the 2014 timeline. If you would like to discuss any of these ideas, or are thinking of applying to work with us, please send an email to the [https://groups.google.com/forum/?fromgroups#!forum/open-lighting Open Lighting List] introducing yourself.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Please also see the [[GSOC Challenge]] page. You should complete this before applying.&lt;br /&gt;
&lt;br /&gt;
== RESTful API ==&lt;br /&gt;
&lt;br /&gt;
The current API that the website uses is a bit old and needs updated to allow full use of OLA's inner working in a general RESTful way. This would allow third parties to easily build new web based apps that could connect to RDM and DMX devices.&lt;br /&gt;
&lt;br /&gt;
This project would include:&lt;br /&gt;
* Writing and testing the new API&lt;br /&gt;
* Modifying our current Web app to use the new web api&lt;br /&gt;
&amp;lt;br/&amp;gt;&lt;br /&gt;
'''Skills Required''': C++, Javascript, HTML, JSON &amp;lt;br/&amp;gt;&lt;br /&gt;
'''Estimated Difficulty''': Easy&lt;br /&gt;
&lt;br /&gt;
==Port to Android==&lt;br /&gt;
&lt;br /&gt;
Android is an obvious target for [[OLA]]. Not only does it make perfect sense to use phones &amp;amp; tablets as lighting control interfaces but the Android platform could be used to build embedded lighting control devices. A small amount of this has been done, see [[OLA on Android]]. [https://code.google.com/p/open-lighting/issues/detail?id=221 Bug #221] covers this work.&lt;br /&gt;
&lt;br /&gt;
This project would include:&lt;br /&gt;
* Building OLA as a Android Application&lt;br /&gt;
* Adding a [http://code.google.com/p/linux-lighting/issues/detail?id=15&amp;amp;colspec=ID%20Type%20Status%20Priority%20Component%20Milestone%20Summary Java client] or wrapping the C++ client with a Java library.&lt;br /&gt;
* Writing a frontend in Java to demonstrate the capabilities of OLA. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Skills Required''': C++, Java, Android &amp;lt;br/&amp;gt;&lt;br /&gt;
'''Estimated Difficulty''': Hard&lt;br /&gt;
&lt;br /&gt;
==Port to Windows ==&lt;br /&gt;
&lt;br /&gt;
This is the most requested 'feature' and would significantly expand the reach of the project especially as we approach v1.0. The current supported method of running OLA on Windows is using VMWare  ([[OLA_on_Windows_with_VMWare|instructions]]). This is sub optimal, since it requires the use of non-free software, is challenging for users without unix command line experience, and doesn't allow Windows applications to communicate with OLA.  Work on a Windows port commenced in mid 2011 (see [[Building_OLA_for_Windows|these Notes]]), but was postponed due to lack of resources.&lt;br /&gt;
&lt;br /&gt;
This project would include:&lt;br /&gt;
* Refactoring the base classes under [http://code.google.com/p/linux-lighting/source/browse/#git%2Fcommon%2Fnetwork common/network] to use the Windows network &amp;amp; event management APIs and ensuring that all unit tests pass. &lt;br /&gt;
* Cleaning up various parts of the code which use POSIX APIs (see http://code.google.com/p/linux-lighting/issues/detail?id=139 for an example)&lt;br /&gt;
&lt;br /&gt;
A Windows port would enable lighting controller applications like [[QLC]] and [[D::Light]] to move to OLA entirely, and not have to maintain their own plugins.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''Skills Required''': C++, Windows Network Programming &amp;amp; Windows Event Handling&amp;lt;br/&amp;gt;&lt;br /&gt;
'''Estimated Difficulty''': Hard&lt;br /&gt;
&lt;br /&gt;
== Asynchronous Web Notification of RDM Messages == &lt;br /&gt;
&lt;br /&gt;
Thanks to sites like GMail and Facebook, users have come to expect asynchronous notification of events in their web browser. [[RDM]] enabled lighting devices can generate events such as ''Over Temperature'' and ''Lamp Faulty'' so it would be nice to alert the users to this. This project would involve work with two Open Source efforts. The student would need to work with [http://www.gnu.org/software/libmicrohttpd/ libmicrohttpd] to add [http://en.wikipedia.org/wiki/WebSocket WebSocket] support (see the [http://lists.gnu.org/archive/html/libmicrohttpd/2012-01/msg00015.html email thread]).&lt;br /&gt;
&lt;br /&gt;
The second step would involve using WebSockets to deliver events to the browser, and building a UI to notify the user. The [[OLA]] UI is built with [http://code.google.com/closure/ Google Closure].&lt;br /&gt;
&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''Skills Required''': C++, Network Programming, Javascript, HTML, Google Closure&amp;lt;br/&amp;gt;&lt;br /&gt;
'''Estimated Difficulty''': Medium&lt;br /&gt;
&lt;br /&gt;
== Web Based Configuration of Preferences ==&lt;br /&gt;
&lt;br /&gt;
User Preferences for [[OLA]] are stored in text files but the web UI provides no method for changing any preferences beyond port patchings. At the moment the user is required to stop the OLA Daemon, exit the text files and restart if settings are to be changed.  This project would involve building a generic preference store and exposing it through the web UI. Changing preferences on the fly is likely to expose bugs in some of the OLA plugins. These will need to be fixed.&lt;br /&gt;
&lt;br /&gt;
'''Skills Required''': C++, Javascript, HTML   &amp;lt;br/&amp;gt;&lt;br /&gt;
'''Estimated Difficulty''': Easy&lt;br /&gt;
&lt;br /&gt;
== Patcher v2 ==&lt;br /&gt;
&lt;br /&gt;
Patcher v2 is one of the next big projects for [[OLA]] it requires a rewrite of our current daemon to allow users to patch a specific channel:universe to a different channel:universe. It would most likely not be entirely up to the student but would be a small team effort as this touches all major points of our system. This would also require a change in the web interface to possibly allow drag and drop of patching. Depending on the students knowledge they may help with the web interface, web backend or the OLA daemon.&lt;br /&gt;
&lt;br /&gt;
'''Skills Required''': C++, Javascript, HTML   &amp;lt;br/&amp;gt;&lt;br /&gt;
'''Estimated Difficulty''': Hard&lt;/div&gt;</summary>
		<author><name>Nightrune</name></author>	</entry>

	<entry>
		<id>https://wiki.openlighting.org/index.php?title=OLP_SOC_Ideas_Page&amp;diff=5648</id>
		<title>OLP SOC Ideas Page</title>
		<link rel="alternate" type="text/html" href="https://wiki.openlighting.org/index.php?title=OLP_SOC_Ideas_Page&amp;diff=5648"/>
				<updated>2014-02-13T16:42:32Z</updated>
		
		<summary type="html">&lt;p&gt;Nightrune: /* Port to Windows */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This page lists some ideas for [http://www.google-melange.com/gsoc/homepage/google/gsoc2014 Google Summer of Code 2014] projects for the [[Open Lighting Project]]. You can use these ideas as a basis for your application, or come up with something different. Please see the Google SOC site for the 2014 timeline. If you would like to discuss any of these ideas, or are thinking of applying to work with us, please send an email to the [https://groups.google.com/forum/?fromgroups#!forum/open-lighting Open Lighting List] introducing yourself.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Please also see the [[GSOC Challenge]] page. You should complete this before applying.&lt;br /&gt;
&lt;br /&gt;
== RESTful API ==&lt;br /&gt;
&lt;br /&gt;
The current API that the website uses is a bit old and needs updated to allow full use of OLA's inner working in a general RESTful way. This would allow third parties to easily build new web based apps that could connect to RDM and DMX devices.&lt;br /&gt;
&lt;br /&gt;
This project would include:&lt;br /&gt;
* Writing and testing the new API&lt;br /&gt;
* Modifying our current Web app to use the new web api&lt;br /&gt;
&amp;lt;br/&amp;gt;&lt;br /&gt;
'''Skills Required''': C++, Javascript, HTML, JSON &amp;lt;br/&amp;gt;&lt;br /&gt;
'''Estimated Difficulty''': Easy&lt;br /&gt;
&lt;br /&gt;
==Port to Android==&lt;br /&gt;
&lt;br /&gt;
Android is an obvious target for [[OLA]]. Not only does it make perfect sense to use phones &amp;amp; tablets as lighting control interfaces but the Android platform could be used to build embedded lighting control devices. A small amount of this has been done, see [[OLA on Android]]. [https://code.google.com/p/open-lighting/issues/detail?id=221 Bug #221] covers this work.&lt;br /&gt;
&lt;br /&gt;
This project would include:&lt;br /&gt;
* Building OLA as a Android Application&lt;br /&gt;
* Adding a [http://code.google.com/p/linux-lighting/issues/detail?id=15&amp;amp;colspec=ID%20Type%20Status%20Priority%20Component%20Milestone%20Summary Java client] or wrapping the C++ client with a Java library.&lt;br /&gt;
* Writing a frontend in Java to demonstrate the capabilities of OLA. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Skills Required''': C++, Java, Android &amp;lt;br/&amp;gt;&lt;br /&gt;
'''Estimated Difficulty''': Hard&lt;br /&gt;
&lt;br /&gt;
==Port to Windows ==&lt;br /&gt;
&lt;br /&gt;
This is the most requested 'feature' and would significantly expand the reach of the project especially as we approach v1.0. The current supported method of running OLA on Windows is using VMWare  ([[OLA_on_Windows_with_VMWare|instructions]]). This is sub optimal, since it requires the use of non-free software, is challenging for users without unix command line experience, and doesn't allow Windows applications to communicate with OLA.  Work on a Windows port commenced in mid 2011 (see [[Building_OLA_for_Windows|these Notes]]), but was postponed due to lack of resources.&lt;br /&gt;
&lt;br /&gt;
This project would include:&lt;br /&gt;
* Refactoring the base classes under [http://code.google.com/p/linux-lighting/source/browse/#git%2Fcommon%2Fnetwork common/network] to use the Windows network &amp;amp; event management APIs and ensuring that all unit tests pass. &lt;br /&gt;
* Cleaning up various parts of the code which use POSIX APIs (see http://code.google.com/p/linux-lighting/issues/detail?id=139 for an example)&lt;br /&gt;
&lt;br /&gt;
A Windows port would enable lighting controller applications like [[QLC]] and [[D::Light]] to move to OLA entirely, and not have to maintain their own plugins.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''Skills Required''': C++, Windows Network Programming &amp;amp; Windows Event Handling&amp;lt;br/&amp;gt;&lt;br /&gt;
'''Estimated Difficulty''': Hard&lt;br /&gt;
&lt;br /&gt;
== Asynchronous Web Notification of RDM Messages == &lt;br /&gt;
&lt;br /&gt;
Thanks to sites like GMail and Facebook, users have come to expect asynchronous notification of events in their web browser. [[RDM]] enabled lighting devices can generate events such as ''Over Temperature'' and ''Lamp Faulty'' so it would be nice to alert the users to this. This project would involve work with two Open Source efforts. The student would need to work with [http://www.gnu.org/software/libmicrohttpd/ libmicrohttpd] to add [http://en.wikipedia.org/wiki/WebSocket WebSocket] support (see the [http://lists.gnu.org/archive/html/libmicrohttpd/2012-01/msg00015.html email thread]).&lt;br /&gt;
&lt;br /&gt;
The second step would involve using WebSockets to deliver events to the browser, and building a UI to notify the user. The [[OLA]] UI is built with [http://code.google.com/closure/ Google Closure].&lt;br /&gt;
&lt;br /&gt;
'''Skills Required''': C++, Network Programming, Javascript, HTML, Google Closure&amp;lt;br/&amp;gt;&lt;br /&gt;
'''Estimated Difficulty''': Medium&lt;br /&gt;
&lt;br /&gt;
== Web Based Configuration of Preferences ==&lt;br /&gt;
&lt;br /&gt;
User Preferences for [[OLA]] are stored in text files but the web UI provides no method for changing any preferences beyond port patchings. At the moment the user is required to stop the OLA Daemon, exit the text files and restart if settings are to be changed.  This project would involve building a generic preference store and exposing it through the web UI. Changing preferences on the fly is likely to expose bugs in some of the OLA plugins. These will need to be fixed.&lt;br /&gt;
&lt;br /&gt;
'''Skills Required''': C++, Javascript, HTML   &amp;lt;br/&amp;gt;&lt;br /&gt;
'''Estimated Difficulty''': Easy&lt;br /&gt;
&lt;br /&gt;
== Patcher v2 ==&lt;br /&gt;
&lt;br /&gt;
Patcher v2 is one of the next big projects for [[OLA]] it requires a rewrite of our current daemon to allow users to patch a specific channel:universe to a different channel:universe. It would most likely not be entirely up to the student but would be a small team effort as this touches all major points of our system. This would also require a change in the web interface to possibly allow drag and drop of patching. Depending on the students knowledge they may help with the web interface, web backend or the OLA daemon.&lt;br /&gt;
&lt;br /&gt;
'''Skills Required''': C++, Javascript, HTML   &amp;lt;br/&amp;gt;&lt;br /&gt;
'''Estimated Difficulty''': Hard&lt;/div&gt;</summary>
		<author><name>Nightrune</name></author>	</entry>

	<entry>
		<id>https://wiki.openlighting.org/index.php?title=OLP_SOC_Ideas_Page&amp;diff=5647</id>
		<title>OLP SOC Ideas Page</title>
		<link rel="alternate" type="text/html" href="https://wiki.openlighting.org/index.php?title=OLP_SOC_Ideas_Page&amp;diff=5647"/>
				<updated>2014-02-13T16:42:14Z</updated>
		
		<summary type="html">&lt;p&gt;Nightrune: /* Port to Windows */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This page lists some ideas for [http://www.google-melange.com/gsoc/homepage/google/gsoc2014 Google Summer of Code 2014] projects for the [[Open Lighting Project]]. You can use these ideas as a basis for your application, or come up with something different. Please see the Google SOC site for the 2014 timeline. If you would like to discuss any of these ideas, or are thinking of applying to work with us, please send an email to the [https://groups.google.com/forum/?fromgroups#!forum/open-lighting Open Lighting List] introducing yourself.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Please also see the [[GSOC Challenge]] page. You should complete this before applying.&lt;br /&gt;
&lt;br /&gt;
== RESTful API ==&lt;br /&gt;
&lt;br /&gt;
The current API that the website uses is a bit old and needs updated to allow full use of OLA's inner working in a general RESTful way. This would allow third parties to easily build new web based apps that could connect to RDM and DMX devices.&lt;br /&gt;
&lt;br /&gt;
This project would include:&lt;br /&gt;
* Writing and testing the new API&lt;br /&gt;
* Modifying our current Web app to use the new web api&lt;br /&gt;
&amp;lt;br/&amp;gt;&lt;br /&gt;
'''Skills Required''': C++, Javascript, HTML, JSON &amp;lt;br/&amp;gt;&lt;br /&gt;
'''Estimated Difficulty''': Easy&lt;br /&gt;
&lt;br /&gt;
==Port to Android==&lt;br /&gt;
&lt;br /&gt;
Android is an obvious target for [[OLA]]. Not only does it make perfect sense to use phones &amp;amp; tablets as lighting control interfaces but the Android platform could be used to build embedded lighting control devices. A small amount of this has been done, see [[OLA on Android]]. [https://code.google.com/p/open-lighting/issues/detail?id=221 Bug #221] covers this work.&lt;br /&gt;
&lt;br /&gt;
This project would include:&lt;br /&gt;
* Building OLA as a Android Application&lt;br /&gt;
* Adding a [http://code.google.com/p/linux-lighting/issues/detail?id=15&amp;amp;colspec=ID%20Type%20Status%20Priority%20Component%20Milestone%20Summary Java client] or wrapping the C++ client with a Java library.&lt;br /&gt;
* Writing a frontend in Java to demonstrate the capabilities of OLA. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Skills Required''': C++, Java, Android &amp;lt;br/&amp;gt;&lt;br /&gt;
'''Estimated Difficulty''': Hard&lt;br /&gt;
&lt;br /&gt;
==Port to Windows ==&lt;br /&gt;
&lt;br /&gt;
This is the most requested 'feature' and would significantly expand the reach of the project especially as we approach v1.0. The current supported method of running OLA on Windows is using VMWare  ([[OLA_on_Windows_with_VMWare|instructions]]). This is sub optimal, since it requires the use of non-free software, is challenging for users without unix command line experience, and doesn't allow Windows applications to communicate with OLA.  Work on a Windows port commenced in mid 2011 (see [[Building_OLA_for_Windows|these Notes]]), but was postponed due to lack of resources.&lt;br /&gt;
&lt;br /&gt;
This project would include:&lt;br /&gt;
* Refactoring the base classes under [http://code.google.com/p/linux-lighting/source/browse/#git%2Fcommon%2Fnetwork common/network] to use the Windows network &amp;amp; event management APIs and ensuring that all unit tests pass. &lt;br /&gt;
* Cleaning up various parts of the code which use POSIX APIs (see http://code.google.com/p/linux-lighting/issues/detail?id=139 for an example)&lt;br /&gt;
&lt;br /&gt;
A Windows port would enable lighting controller applications like [[QLC]] and [[D::Light]] to move to OLA entirely, and not have to maintain their own plugins.&lt;br /&gt;
&amp;lt;br/&amp;gt;&lt;br /&gt;
'''Skills Required''': C++, Windows Network Programming &amp;amp; Windows Event Handling&amp;lt;br/&amp;gt;&lt;br /&gt;
'''Estimated Difficulty''': Hard&lt;br /&gt;
&lt;br /&gt;
== Asynchronous Web Notification of RDM Messages == &lt;br /&gt;
&lt;br /&gt;
Thanks to sites like GMail and Facebook, users have come to expect asynchronous notification of events in their web browser. [[RDM]] enabled lighting devices can generate events such as ''Over Temperature'' and ''Lamp Faulty'' so it would be nice to alert the users to this. This project would involve work with two Open Source efforts. The student would need to work with [http://www.gnu.org/software/libmicrohttpd/ libmicrohttpd] to add [http://en.wikipedia.org/wiki/WebSocket WebSocket] support (see the [http://lists.gnu.org/archive/html/libmicrohttpd/2012-01/msg00015.html email thread]).&lt;br /&gt;
&lt;br /&gt;
The second step would involve using WebSockets to deliver events to the browser, and building a UI to notify the user. The [[OLA]] UI is built with [http://code.google.com/closure/ Google Closure].&lt;br /&gt;
&lt;br /&gt;
'''Skills Required''': C++, Network Programming, Javascript, HTML, Google Closure&amp;lt;br/&amp;gt;&lt;br /&gt;
'''Estimated Difficulty''': Medium&lt;br /&gt;
&lt;br /&gt;
== Web Based Configuration of Preferences ==&lt;br /&gt;
&lt;br /&gt;
User Preferences for [[OLA]] are stored in text files but the web UI provides no method for changing any preferences beyond port patchings. At the moment the user is required to stop the OLA Daemon, exit the text files and restart if settings are to be changed.  This project would involve building a generic preference store and exposing it through the web UI. Changing preferences on the fly is likely to expose bugs in some of the OLA plugins. These will need to be fixed.&lt;br /&gt;
&lt;br /&gt;
'''Skills Required''': C++, Javascript, HTML   &amp;lt;br/&amp;gt;&lt;br /&gt;
'''Estimated Difficulty''': Easy&lt;br /&gt;
&lt;br /&gt;
== Patcher v2 ==&lt;br /&gt;
&lt;br /&gt;
Patcher v2 is one of the next big projects for [[OLA]] it requires a rewrite of our current daemon to allow users to patch a specific channel:universe to a different channel:universe. It would most likely not be entirely up to the student but would be a small team effort as this touches all major points of our system. This would also require a change in the web interface to possibly allow drag and drop of patching. Depending on the students knowledge they may help with the web interface, web backend or the OLA daemon.&lt;br /&gt;
&lt;br /&gt;
'''Skills Required''': C++, Javascript, HTML   &amp;lt;br/&amp;gt;&lt;br /&gt;
'''Estimated Difficulty''': Hard&lt;/div&gt;</summary>
		<author><name>Nightrune</name></author>	</entry>

	<entry>
		<id>https://wiki.openlighting.org/index.php?title=OLP_SOC_Ideas_Page&amp;diff=5646</id>
		<title>OLP SOC Ideas Page</title>
		<link rel="alternate" type="text/html" href="https://wiki.openlighting.org/index.php?title=OLP_SOC_Ideas_Page&amp;diff=5646"/>
				<updated>2014-02-13T16:42:03Z</updated>
		
		<summary type="html">&lt;p&gt;Nightrune: /* RESTful API */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This page lists some ideas for [http://www.google-melange.com/gsoc/homepage/google/gsoc2014 Google Summer of Code 2014] projects for the [[Open Lighting Project]]. You can use these ideas as a basis for your application, or come up with something different. Please see the Google SOC site for the 2014 timeline. If you would like to discuss any of these ideas, or are thinking of applying to work with us, please send an email to the [https://groups.google.com/forum/?fromgroups#!forum/open-lighting Open Lighting List] introducing yourself.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Please also see the [[GSOC Challenge]] page. You should complete this before applying.&lt;br /&gt;
&lt;br /&gt;
== RESTful API ==&lt;br /&gt;
&lt;br /&gt;
The current API that the website uses is a bit old and needs updated to allow full use of OLA's inner working in a general RESTful way. This would allow third parties to easily build new web based apps that could connect to RDM and DMX devices.&lt;br /&gt;
&lt;br /&gt;
This project would include:&lt;br /&gt;
* Writing and testing the new API&lt;br /&gt;
* Modifying our current Web app to use the new web api&lt;br /&gt;
&amp;lt;br/&amp;gt;&lt;br /&gt;
'''Skills Required''': C++, Javascript, HTML, JSON &amp;lt;br/&amp;gt;&lt;br /&gt;
'''Estimated Difficulty''': Easy&lt;br /&gt;
&lt;br /&gt;
==Port to Android==&lt;br /&gt;
&lt;br /&gt;
Android is an obvious target for [[OLA]]. Not only does it make perfect sense to use phones &amp;amp; tablets as lighting control interfaces but the Android platform could be used to build embedded lighting control devices. A small amount of this has been done, see [[OLA on Android]]. [https://code.google.com/p/open-lighting/issues/detail?id=221 Bug #221] covers this work.&lt;br /&gt;
&lt;br /&gt;
This project would include:&lt;br /&gt;
* Building OLA as a Android Application&lt;br /&gt;
* Adding a [http://code.google.com/p/linux-lighting/issues/detail?id=15&amp;amp;colspec=ID%20Type%20Status%20Priority%20Component%20Milestone%20Summary Java client] or wrapping the C++ client with a Java library.&lt;br /&gt;
* Writing a frontend in Java to demonstrate the capabilities of OLA. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Skills Required''': C++, Java, Android &amp;lt;br/&amp;gt;&lt;br /&gt;
'''Estimated Difficulty''': Hard&lt;br /&gt;
&lt;br /&gt;
==Port to Windows ==&lt;br /&gt;
&lt;br /&gt;
This is the most requested 'feature' and would significantly expand the reach of the project especially as we approach v1.0. The current supported method of running OLA on Windows is using VMWare  ([[OLA_on_Windows_with_VMWare|instructions]]). This is sub optimal, since it requires the use of non-free software, is challenging for users without unix command line experience, and doesn't allow Windows applications to communicate with OLA.  Work on a Windows port commenced in mid 2011 (see [[Building_OLA_for_Windows|these Notes]]), but was postponed due to lack of resources.&lt;br /&gt;
&lt;br /&gt;
This project would include:&lt;br /&gt;
* Refactoring the base classes under [http://code.google.com/p/linux-lighting/source/browse/#git%2Fcommon%2Fnetwork common/network] to use the Windows network &amp;amp; event management APIs and ensuring that all unit tests pass. &lt;br /&gt;
* Cleaning up various parts of the code which use POSIX APIs (see http://code.google.com/p/linux-lighting/issues/detail?id=139 for an example)&lt;br /&gt;
&lt;br /&gt;
A Windows port would enable lighting controller applications like [[QLC]] and [[D::Light]] to move to OLA entirely, and not have to maintain their own plugins.&lt;br /&gt;
&lt;br /&gt;
'''Skills Required''': C++, Windows Network Programming &amp;amp; Windows Event Handling&amp;lt;br/&amp;gt;&lt;br /&gt;
'''Estimated Difficulty''': Hard&lt;br /&gt;
&lt;br /&gt;
== Asynchronous Web Notification of RDM Messages == &lt;br /&gt;
&lt;br /&gt;
Thanks to sites like GMail and Facebook, users have come to expect asynchronous notification of events in their web browser. [[RDM]] enabled lighting devices can generate events such as ''Over Temperature'' and ''Lamp Faulty'' so it would be nice to alert the users to this. This project would involve work with two Open Source efforts. The student would need to work with [http://www.gnu.org/software/libmicrohttpd/ libmicrohttpd] to add [http://en.wikipedia.org/wiki/WebSocket WebSocket] support (see the [http://lists.gnu.org/archive/html/libmicrohttpd/2012-01/msg00015.html email thread]).&lt;br /&gt;
&lt;br /&gt;
The second step would involve using WebSockets to deliver events to the browser, and building a UI to notify the user. The [[OLA]] UI is built with [http://code.google.com/closure/ Google Closure].&lt;br /&gt;
&lt;br /&gt;
'''Skills Required''': C++, Network Programming, Javascript, HTML, Google Closure&amp;lt;br/&amp;gt;&lt;br /&gt;
'''Estimated Difficulty''': Medium&lt;br /&gt;
&lt;br /&gt;
== Web Based Configuration of Preferences ==&lt;br /&gt;
&lt;br /&gt;
User Preferences for [[OLA]] are stored in text files but the web UI provides no method for changing any preferences beyond port patchings. At the moment the user is required to stop the OLA Daemon, exit the text files and restart if settings are to be changed.  This project would involve building a generic preference store and exposing it through the web UI. Changing preferences on the fly is likely to expose bugs in some of the OLA plugins. These will need to be fixed.&lt;br /&gt;
&lt;br /&gt;
'''Skills Required''': C++, Javascript, HTML   &amp;lt;br/&amp;gt;&lt;br /&gt;
'''Estimated Difficulty''': Easy&lt;br /&gt;
&lt;br /&gt;
== Patcher v2 ==&lt;br /&gt;
&lt;br /&gt;
Patcher v2 is one of the next big projects for [[OLA]] it requires a rewrite of our current daemon to allow users to patch a specific channel:universe to a different channel:universe. It would most likely not be entirely up to the student but would be a small team effort as this touches all major points of our system. This would also require a change in the web interface to possibly allow drag and drop of patching. Depending on the students knowledge they may help with the web interface, web backend or the OLA daemon.&lt;br /&gt;
&lt;br /&gt;
'''Skills Required''': C++, Javascript, HTML   &amp;lt;br/&amp;gt;&lt;br /&gt;
'''Estimated Difficulty''': Hard&lt;/div&gt;</summary>
		<author><name>Nightrune</name></author>	</entry>

	<entry>
		<id>https://wiki.openlighting.org/index.php?title=OLP_SOC_Ideas_Page&amp;diff=5645</id>
		<title>OLP SOC Ideas Page</title>
		<link rel="alternate" type="text/html" href="https://wiki.openlighting.org/index.php?title=OLP_SOC_Ideas_Page&amp;diff=5645"/>
				<updated>2014-02-13T16:41:38Z</updated>
		
		<summary type="html">&lt;p&gt;Nightrune: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This page lists some ideas for [http://www.google-melange.com/gsoc/homepage/google/gsoc2014 Google Summer of Code 2014] projects for the [[Open Lighting Project]]. You can use these ideas as a basis for your application, or come up with something different. Please see the Google SOC site for the 2014 timeline. If you would like to discuss any of these ideas, or are thinking of applying to work with us, please send an email to the [https://groups.google.com/forum/?fromgroups#!forum/open-lighting Open Lighting List] introducing yourself.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Please also see the [[GSOC Challenge]] page. You should complete this before applying.&lt;br /&gt;
&lt;br /&gt;
== RESTful API ==&lt;br /&gt;
&lt;br /&gt;
The current API that the website uses is a bit old and needs updated to allow full use of OLA's inner working in a general RESTful way. This would allow third parties to easily build new web based apps that could connect to RDM and DMX devices.&lt;br /&gt;
&lt;br /&gt;
This project would include:&lt;br /&gt;
* Writing and testing the new API&lt;br /&gt;
* Modifying our current Web app to use the new web api&lt;br /&gt;
&lt;br /&gt;
'''Skills Required''': C++, Javascript, HTML, JSON &amp;lt;br/&amp;gt;&lt;br /&gt;
'''Estimated Difficulty''': Easy&lt;br /&gt;
&lt;br /&gt;
==Port to Android==&lt;br /&gt;
&lt;br /&gt;
Android is an obvious target for [[OLA]]. Not only does it make perfect sense to use phones &amp;amp; tablets as lighting control interfaces but the Android platform could be used to build embedded lighting control devices. A small amount of this has been done, see [[OLA on Android]]. [https://code.google.com/p/open-lighting/issues/detail?id=221 Bug #221] covers this work.&lt;br /&gt;
&lt;br /&gt;
This project would include:&lt;br /&gt;
* Building OLA as a Android Application&lt;br /&gt;
* Adding a [http://code.google.com/p/linux-lighting/issues/detail?id=15&amp;amp;colspec=ID%20Type%20Status%20Priority%20Component%20Milestone%20Summary Java client] or wrapping the C++ client with a Java library.&lt;br /&gt;
* Writing a frontend in Java to demonstrate the capabilities of OLA. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Skills Required''': C++, Java, Android &amp;lt;br/&amp;gt;&lt;br /&gt;
'''Estimated Difficulty''': Hard&lt;br /&gt;
&lt;br /&gt;
==Port to Windows ==&lt;br /&gt;
&lt;br /&gt;
This is the most requested 'feature' and would significantly expand the reach of the project especially as we approach v1.0. The current supported method of running OLA on Windows is using VMWare  ([[OLA_on_Windows_with_VMWare|instructions]]). This is sub optimal, since it requires the use of non-free software, is challenging for users without unix command line experience, and doesn't allow Windows applications to communicate with OLA.  Work on a Windows port commenced in mid 2011 (see [[Building_OLA_for_Windows|these Notes]]), but was postponed due to lack of resources.&lt;br /&gt;
&lt;br /&gt;
This project would include:&lt;br /&gt;
* Refactoring the base classes under [http://code.google.com/p/linux-lighting/source/browse/#git%2Fcommon%2Fnetwork common/network] to use the Windows network &amp;amp; event management APIs and ensuring that all unit tests pass. &lt;br /&gt;
* Cleaning up various parts of the code which use POSIX APIs (see http://code.google.com/p/linux-lighting/issues/detail?id=139 for an example)&lt;br /&gt;
&lt;br /&gt;
A Windows port would enable lighting controller applications like [[QLC]] and [[D::Light]] to move to OLA entirely, and not have to maintain their own plugins.&lt;br /&gt;
&lt;br /&gt;
'''Skills Required''': C++, Windows Network Programming &amp;amp; Windows Event Handling&amp;lt;br/&amp;gt;&lt;br /&gt;
'''Estimated Difficulty''': Hard&lt;br /&gt;
&lt;br /&gt;
== Asynchronous Web Notification of RDM Messages == &lt;br /&gt;
&lt;br /&gt;
Thanks to sites like GMail and Facebook, users have come to expect asynchronous notification of events in their web browser. [[RDM]] enabled lighting devices can generate events such as ''Over Temperature'' and ''Lamp Faulty'' so it would be nice to alert the users to this. This project would involve work with two Open Source efforts. The student would need to work with [http://www.gnu.org/software/libmicrohttpd/ libmicrohttpd] to add [http://en.wikipedia.org/wiki/WebSocket WebSocket] support (see the [http://lists.gnu.org/archive/html/libmicrohttpd/2012-01/msg00015.html email thread]).&lt;br /&gt;
&lt;br /&gt;
The second step would involve using WebSockets to deliver events to the browser, and building a UI to notify the user. The [[OLA]] UI is built with [http://code.google.com/closure/ Google Closure].&lt;br /&gt;
&lt;br /&gt;
'''Skills Required''': C++, Network Programming, Javascript, HTML, Google Closure&amp;lt;br/&amp;gt;&lt;br /&gt;
'''Estimated Difficulty''': Medium&lt;br /&gt;
&lt;br /&gt;
== Web Based Configuration of Preferences ==&lt;br /&gt;
&lt;br /&gt;
User Preferences for [[OLA]] are stored in text files but the web UI provides no method for changing any preferences beyond port patchings. At the moment the user is required to stop the OLA Daemon, exit the text files and restart if settings are to be changed.  This project would involve building a generic preference store and exposing it through the web UI. Changing preferences on the fly is likely to expose bugs in some of the OLA plugins. These will need to be fixed.&lt;br /&gt;
&lt;br /&gt;
'''Skills Required''': C++, Javascript, HTML   &amp;lt;br/&amp;gt;&lt;br /&gt;
'''Estimated Difficulty''': Easy&lt;br /&gt;
&lt;br /&gt;
== Patcher v2 ==&lt;br /&gt;
&lt;br /&gt;
Patcher v2 is one of the next big projects for [[OLA]] it requires a rewrite of our current daemon to allow users to patch a specific channel:universe to a different channel:universe. It would most likely not be entirely up to the student but would be a small team effort as this touches all major points of our system. This would also require a change in the web interface to possibly allow drag and drop of patching. Depending on the students knowledge they may help with the web interface, web backend or the OLA daemon.&lt;br /&gt;
&lt;br /&gt;
'''Skills Required''': C++, Javascript, HTML   &amp;lt;br/&amp;gt;&lt;br /&gt;
'''Estimated Difficulty''': Hard&lt;/div&gt;</summary>
		<author><name>Nightrune</name></author>	</entry>

	<entry>
		<id>https://wiki.openlighting.org/index.php?title=OLP_SOC_Ideas_Page&amp;diff=5644</id>
		<title>OLP SOC Ideas Page</title>
		<link rel="alternate" type="text/html" href="https://wiki.openlighting.org/index.php?title=OLP_SOC_Ideas_Page&amp;diff=5644"/>
				<updated>2014-02-13T16:38:49Z</updated>
		
		<summary type="html">&lt;p&gt;Nightrune: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This page lists some ideas for [http://www.google-melange.com/gsoc/homepage/google/gsoc2014 Google Summer of Code 2014] projects for the [[Open Lighting Project]]. You can use these ideas as a basis for your application, or come up with something different. Please see the Google SOC site for the 2014 timeline. If you would like to discuss any of these ideas, or are thinking of applying to work with us, please send an email to the [https://groups.google.com/forum/?fromgroups#!forum/open-lighting Open Lighting List] introducing yourself.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Please also see the [[GSOC Challenge]] page. You should complete this before applying.&lt;br /&gt;
&lt;br /&gt;
== RESTful API ==&lt;br /&gt;
&lt;br /&gt;
The current API that the website uses is a bit old and needs updated to allow full use of OLA's inner working in a general RESTful way. This would allow third parties to easily build new web based apps that could connect to RDM and DMX devices.&lt;br /&gt;
&lt;br /&gt;
'''Skills Required''': C++, Javascript, HTML, JSON &amp;lt;br/&amp;gt;&lt;br /&gt;
'''Estimated Difficulty''': Easy&lt;br /&gt;
&lt;br /&gt;
==Port to Android==&lt;br /&gt;
&lt;br /&gt;
Android is an obvious target for [[OLA]]. Not only does it make perfect sense to use phones &amp;amp; tablets as lighting control interfaces but the Android platform could be used to build embedded lighting control devices. A small amount of this has been done, see [[OLA on Android]]. [https://code.google.com/p/open-lighting/issues/detail?id=221 Bug #221] covers this work.&lt;br /&gt;
&lt;br /&gt;
This project would include:&lt;br /&gt;
* Building OLA as a Android Application&lt;br /&gt;
* Adding a [http://code.google.com/p/linux-lighting/issues/detail?id=15&amp;amp;colspec=ID%20Type%20Status%20Priority%20Component%20Milestone%20Summary Java client] or wrapping the C++ client with a Java library.&lt;br /&gt;
* Writing a frontend in Java to demonstrate the capabilities of OLA. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Skills Required''': C++, Java, Android &amp;lt;br/&amp;gt;&lt;br /&gt;
'''Estimated Difficulty''': Hard&lt;br /&gt;
&lt;br /&gt;
==Port to Windows ==&lt;br /&gt;
&lt;br /&gt;
This is the most requested 'feature' and would significantly expand the reach of the project especially as we approach v1.0. The current supported method of running OLA on Windows is using VMWare  ([[OLA_on_Windows_with_VMWare|instructions]]). This is sub optimal, since it requires the use of non-free software, is challenging for users without unix command line experience, and doesn't allow Windows applications to communicate with OLA.  Work on a Windows port commenced in mid 2011 (see [[Building_OLA_for_Windows|these Notes]]), but was postponed due to lack of resources.&lt;br /&gt;
&lt;br /&gt;
This project would include:&lt;br /&gt;
* Refactoring the base classes under [http://code.google.com/p/linux-lighting/source/browse/#git%2Fcommon%2Fnetwork common/network] to use the Windows network &amp;amp; event management APIs and ensuring that all unit tests pass. &lt;br /&gt;
* Cleaning up various parts of the code which use POSIX APIs (see http://code.google.com/p/linux-lighting/issues/detail?id=139 for an example)&lt;br /&gt;
&lt;br /&gt;
A Windows port would enable lighting controller applications like [[QLC]] and [[D::Light]] to move to OLA entirely, and not have to maintain their own plugins.&lt;br /&gt;
&lt;br /&gt;
'''Skills Required''': C++, Windows Network Programming &amp;amp; Windows Event Handling&amp;lt;br/&amp;gt;&lt;br /&gt;
'''Estimated Difficulty''': Hard&lt;br /&gt;
&lt;br /&gt;
== Asynchronous Web Notification of RDM Messages == &lt;br /&gt;
&lt;br /&gt;
Thanks to sites like GMail and Facebook, users have come to expect asynchronous notification of events in their web browser. [[RDM]] enabled lighting devices can generate events such as ''Over Temperature'' and ''Lamp Faulty'' so it would be nice to alert the users to this. This project would involve work with two Open Source efforts. The student would need to work with [http://www.gnu.org/software/libmicrohttpd/ libmicrohttpd] to add [http://en.wikipedia.org/wiki/WebSocket WebSocket] support (see the [http://lists.gnu.org/archive/html/libmicrohttpd/2012-01/msg00015.html email thread]).&lt;br /&gt;
&lt;br /&gt;
The second step would involve using WebSockets to deliver events to the browser, and building a UI to notify the user. The [[OLA]] UI is built with [http://code.google.com/closure/ Google Closure].&lt;br /&gt;
&lt;br /&gt;
'''Skills Required''': C++, Network Programming, Javascript, HTML, Google Closure&amp;lt;br/&amp;gt;&lt;br /&gt;
'''Estimated Difficulty''': Medium&lt;br /&gt;
&lt;br /&gt;
== Web Based Configuration of Preferences ==&lt;br /&gt;
&lt;br /&gt;
User Preferences for [[OLA]] are stored in text files but the web UI provides no method for changing any preferences beyond port patchings. At the moment the user is required to stop the OLA Daemon, exit the text files and restart if settings are to be changed.  This project would involve building a generic preference store and exposing it through the web UI. Changing preferences on the fly is likely to expose bugs in some of the OLA plugins. These will need to be fixed.&lt;br /&gt;
&lt;br /&gt;
'''Skills Required''': C++, Javascript, HTML   &amp;lt;br/&amp;gt;&lt;br /&gt;
'''Estimated Difficulty''': Easy&lt;br /&gt;
&lt;br /&gt;
== Patcher v2 ==&lt;br /&gt;
&lt;br /&gt;
Patcher v2 is one of the next big projects for [[OLA]] it requires a rewrite of our current daemon to allow users to patch a specific channel:universe to a different channel:universe. It would most likely not be entirely up to the student but would be a small team effort as this touches all major points of our system. This would also require a change in the web interface to possibly allow drag and drop of patching. Depending on the students knowledge they may help with the web interface, web backend or the OLA daemon.&lt;br /&gt;
&lt;br /&gt;
'''Skills Required''': C++, Javascript, HTML   &amp;lt;br/&amp;gt;&lt;br /&gt;
'''Estimated Difficulty''': Hard&lt;/div&gt;</summary>
		<author><name>Nightrune</name></author>	</entry>

	<entry>
		<id>https://wiki.openlighting.org/index.php?title=OLP_SOC_Ideas_Page&amp;diff=5643</id>
		<title>OLP SOC Ideas Page</title>
		<link rel="alternate" type="text/html" href="https://wiki.openlighting.org/index.php?title=OLP_SOC_Ideas_Page&amp;diff=5643"/>
				<updated>2014-02-13T16:36:58Z</updated>
		
		<summary type="html">&lt;p&gt;Nightrune: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This page lists some ideas for [http://www.google-melange.com/gsoc/homepage/google/gsoc2013 Google Summer of Code 2013] projects for the [[Open Lighting Project]]. You can use these ideas as a basis for your application, or come up with something different. Please see the Google SOC site for the 2013 timeline. If you would like to discuss any of these ideas, or are thinking of applying to work with us, please send an email to the [https://groups.google.com/forum/?fromgroups#!forum/open-lighting Open Lighting List] introducing yourself.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Please also see the [[GSOC Challenge]] page. You should complete this before applying.&lt;br /&gt;
&lt;br /&gt;
== RESTful API ==&lt;br /&gt;
&lt;br /&gt;
The current API that the website uses is a bit old and needs updated to allow full use of OLA's inner working in a general RESTful way. This would allow third parties to easily build new web based apps that could connect to RDM and DMX devices.&lt;br /&gt;
&lt;br /&gt;
'''Skills Required''': C++, Javascript, HTML, JSON &amp;lt;br/&amp;gt;&lt;br /&gt;
'''Estimated Difficulty''': Easy&lt;br /&gt;
&lt;br /&gt;
==Port to Android==&lt;br /&gt;
&lt;br /&gt;
Android is an obvious target for [[OLA]]. Not only does it make perfect sense to use phones &amp;amp; tablets as lighting control interfaces but the Android platform could be used to build embedded lighting control devices. A small amount of this has been done, see [[OLA on Android]]. [https://code.google.com/p/open-lighting/issues/detail?id=221 Bug #221] covers this work.&lt;br /&gt;
&lt;br /&gt;
This project would include:&lt;br /&gt;
* Building OLA as a Android Application&lt;br /&gt;
* Adding a [http://code.google.com/p/linux-lighting/issues/detail?id=15&amp;amp;colspec=ID%20Type%20Status%20Priority%20Component%20Milestone%20Summary Java client] or wrapping the C++ client with a Java library.&lt;br /&gt;
* Writing a frontend in Java to demonstrate the capabilities of OLA. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Skills Required''': C++, Java, Android &amp;lt;br/&amp;gt;&lt;br /&gt;
'''Estimated Difficulty''': Hard&lt;br /&gt;
&lt;br /&gt;
==Port to Windows ==&lt;br /&gt;
&lt;br /&gt;
This is the most requested 'feature' and would significantly expand the reach of the project especially as we approach v1.0. The current supported method of running OLA on Windows is using VMWare  ([[OLA_on_Windows_with_VMWare|instructions]]). This is sub optimal, since it requires the use of non-free software, is challenging for users without unix command line experience, and doesn't allow Windows applications to communicate with OLA.  Work on a Windows port commenced in mid 2011 (see [[Building_OLA_for_Windows|these Notes]]), but was postponed due to lack of resources.&lt;br /&gt;
&lt;br /&gt;
This project would include:&lt;br /&gt;
* Refactoring the base classes under [http://code.google.com/p/linux-lighting/source/browse/#git%2Fcommon%2Fnetwork common/network] to use the Windows network &amp;amp; event management APIs and ensuring that all unit tests pass. &lt;br /&gt;
* Cleaning up various parts of the code which use POSIX APIs (see http://code.google.com/p/linux-lighting/issues/detail?id=139 for an example)&lt;br /&gt;
&lt;br /&gt;
A Windows port would enable lighting controller applications like [[QLC]] and [[D::Light]] to move to OLA entirely, and not have to maintain their own plugins.&lt;br /&gt;
&lt;br /&gt;
'''Skills Required''': C++, Windows Network Programming &amp;amp; Windows Event Handling&amp;lt;br/&amp;gt;&lt;br /&gt;
'''Estimated Difficulty''': Hard&lt;br /&gt;
&lt;br /&gt;
== Asynchronous Web Notification of RDM Messages == &lt;br /&gt;
&lt;br /&gt;
Thanks to sites like GMail and Facebook, users have come to expect asynchronous notification of events in their web browser. [[RDM]] enabled lighting devices can generate events such as ''Over Temperature'' and ''Lamp Faulty'' so it would be nice to alert the users to this. This project would involve work with two Open Source efforts. The student would need to work with [http://www.gnu.org/software/libmicrohttpd/ libmicrohttpd] to add [http://en.wikipedia.org/wiki/WebSocket WebSocket] support (see the [http://lists.gnu.org/archive/html/libmicrohttpd/2012-01/msg00015.html email thread]).&lt;br /&gt;
&lt;br /&gt;
The second step would involve using WebSockets to deliver events to the browser, and building a UI to notify the user. The [[OLA]] UI is built with [http://code.google.com/closure/ Google Closure].&lt;br /&gt;
&lt;br /&gt;
'''Skills Required''': C++, Network Programming, Javascript, HTML, Google Closure&amp;lt;br/&amp;gt;&lt;br /&gt;
'''Estimated Difficulty''': Medium&lt;br /&gt;
&lt;br /&gt;
== Web Based Configuration of Preferences ==&lt;br /&gt;
&lt;br /&gt;
User Preferences for [[OLA]] are stored in text files but the web UI provides no method for changing any preferences beyond port patchings. At the moment the user is required to stop the OLA Daemon, exit the text files and restart if settings are to be changed.  This project would involve building a generic preference store and exposing it through the web UI. Changing preferences on the fly is likely to expose bugs in some of the OLA plugins. These will need to be fixed.&lt;br /&gt;
&lt;br /&gt;
'''Skills Required''': C++, Javascript, HTML   &amp;lt;br/&amp;gt;&lt;br /&gt;
'''Estimated Difficulty''': Easy&lt;br /&gt;
&lt;br /&gt;
== Patcher v2 ==&lt;br /&gt;
&lt;br /&gt;
Patcher v2 is one of the next big projects for [[OLA]] it requires a rewrite of our current daemon to allow users to patch a specific channel:universe to a different channel:universe. It would most likely not be entirely up to the student but would be a small team effort as this touches all major points of our system. This would also require a change in the web interface to possibly allow drag and drop of patching. Depending on the students knowledge they may help with the web interface, web backend or the OLA daemon.&lt;br /&gt;
&lt;br /&gt;
'''Skills Required''': C++, Javascript, HTML   &amp;lt;br/&amp;gt;&lt;br /&gt;
'''Estimated Difficulty''': Hard&lt;/div&gt;</summary>
		<author><name>Nightrune</name></author>	</entry>

	<entry>
		<id>https://wiki.openlighting.org/index.php?title=OLA_on_Linux&amp;diff=5597</id>
		<title>OLA on Linux</title>
		<link rel="alternate" type="text/html" href="https://wiki.openlighting.org/index.php?title=OLA_on_Linux&amp;diff=5597"/>
				<updated>2013-10-31T02:51:51Z</updated>
		
		<summary type="html">&lt;p&gt;Nightrune: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This describes how to get [[OLA]] working on a Linux system either from the git repo or by using a [http://code.google.com/p/open-lighting/downloads/list released tarball].&lt;br /&gt;
&lt;br /&gt;
=Install dependencies =&lt;br /&gt;
&lt;br /&gt;
You need a couple of libraries installed for everything to work correctly. Some of these are available as packages in distros but others need to be downloaded and built manually.&lt;br /&gt;
&lt;br /&gt;
First you'll need at least the following:&lt;br /&gt;
* cppunit&lt;br /&gt;
* uuid or ossp uuid&lt;br /&gt;
* pkg-config&lt;br /&gt;
* curses&lt;br /&gt;
* lex (or flex)&lt;br /&gt;
* yacc (or bison)&lt;br /&gt;
* the protocol buffers library   [http://code.google.com/p/protobuf/ http://code.google.com/p/protobuf/] (version 2.3.0 or later)&lt;br /&gt;
* microhttpd  [ftp://ftp.gnu.org/gnu/libmicrohttpd/ ftp://ftp.gnu.org/gnu/libmicrohttpd/] (if you want the web UI). You need version &amp;gt;= 0.4.0 of microhttpd&lt;br /&gt;
&lt;br /&gt;
If you're building from git you'll also need the following:&lt;br /&gt;
&lt;br /&gt;
* libtool&lt;br /&gt;
* automake&lt;br /&gt;
* autoconf&lt;br /&gt;
&lt;br /&gt;
== Debian / Ubuntu ==&lt;br /&gt;
There is a fully packaged version of OLA you can just install, for info see [[OLA Debian / Ubuntu]]. There's also a more specific Ubuntu walkthrough for building [[The Newbie Guide for OLA on Ubuntu]].&lt;br /&gt;
&lt;br /&gt;
Debian/Ubuntu users can install them with apt:&lt;br /&gt;
&lt;br /&gt;
  sudo apt-get install libcppunit-dev libcppunit-1.12-1 uuid-dev pkg-config libncurses5-dev libtool autoconf automake  g++ libmicrohttpd-dev \&lt;br /&gt;
  libmicrohttpd10 protobuf-compiler libprotobuf-lite7 python-protobuf libprotobuf-dev libprotoc-dev zlib1g-dev bison flex make libftdi-dev  libftdi1 libusb-1.0-0-dev liblo-dev &lt;br /&gt;
&lt;br /&gt;
Note: Some distributions may offer libprotobuf-lite6 instead of libprotobuf-lite7, which is an acceptable substitution.&lt;br /&gt;
&lt;br /&gt;
If you're using Ubuntu 12.04 or later you can just use the command above. In earlier versions of Ubuntu the version of libprotobuf is too old, so you'll need to install them by hand. You may also need to install an older version of libmicrohttpd (libmicrohttpd9 rather than libmicrohttpd10).&lt;br /&gt;
&lt;br /&gt;
== Centos 6 / RHEL 6 / Fedora 17 ==&lt;br /&gt;
&lt;br /&gt;
Users of rpm based distributions can install them with yum (protobuf*, libmicrohttpd* and libftdi* are in the EPEL repository):&lt;br /&gt;
&lt;br /&gt;
  sudo yum install flex bison protobuf protobuf-devel uuid-devel cppunit-devel protobuf-python libmicrohttpd-devel libusb-devel libftdi-devel libuuid-devel openslp-devel&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
(The remaining libs already come with the OS installation)&lt;br /&gt;
&lt;br /&gt;
== Other Distributions ==&lt;br /&gt;
&lt;br /&gt;
Install using your package manager, or build everything by hand&lt;br /&gt;
&lt;br /&gt;
If you installed things by hand (rather than using your package manager), you need to run ldconfig as root to pick up the new libraries&lt;br /&gt;
&lt;br /&gt;
  sudo  ldconfig&lt;br /&gt;
&lt;br /&gt;
=Checkout or Download an Archive=&lt;br /&gt;
&lt;br /&gt;
You can either download a tarball, or pull the latest version from the git repo&lt;br /&gt;
&lt;br /&gt;
== Tarball ==&lt;br /&gt;
&lt;br /&gt;
Download the most recent tarball from http://code.google.com/p/open-lighting/downloads/list&lt;br /&gt;
Extract using&lt;br /&gt;
&lt;br /&gt;
  tar -zxf ola-0.X.Y.tar.gz&lt;br /&gt;
  cd ola-0.X.Y&lt;br /&gt;
&lt;br /&gt;
== Git ==&lt;br /&gt;
&lt;br /&gt;
If you don't have '''git''' yet, you'll need to install it with your distro's package manager. On Debian / Ubuntu run:&lt;br /&gt;
&lt;br /&gt;
  sudo apt-get install git&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Check out the git repo with the following command:&lt;br /&gt;
&lt;br /&gt;
  git clone https://code.google.com/p/open-lighting/ ola&lt;br /&gt;
  cd ola&lt;br /&gt;
&lt;br /&gt;
{{ MacOLABuild }}&lt;br /&gt;
&lt;br /&gt;
Finally run ldconfig so you can use the new libraries.&lt;br /&gt;
&lt;br /&gt;
  sudo ldconfig&lt;br /&gt;
&lt;br /&gt;
=Device drivers=&lt;br /&gt;
Note that, for some devices, it is necessary to install drivers for OLA to work with them. For example, the [[Open DMX USB]] device needs an additional kernel module that could be built using the instuctions on [[LLA_and_Q_Light_Controller_Ubuntu_Tutorial]]. For other devices, refer to the corresponding device page on this wiki.&lt;br /&gt;
&lt;br /&gt;
=Known Issues=&lt;br /&gt;
&lt;br /&gt;
If you get an error like the following:&lt;br /&gt;
&lt;br /&gt;
 /bin/sh ./libtool --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I.   -I/opt/local/var/macports/software/protobuf-cpp/2.0.3_0/opt/local/include/  -g -O2 -c -o ltdl.lo ltdl.c&lt;br /&gt;
 ./libtool: line 464: CDPATH: command not found&lt;br /&gt;
 /Users/simonn/lighting/lla/libltdl/libtool: line 464: CDPATH: command not found&lt;br /&gt;
 /Users/simonn/lighting/lla/libltdl/libtool: line 1142: func_opt_split: command not found&lt;br /&gt;
 libtool: Version mismatch error.  This is libtool 2.2.6, but the&lt;br /&gt;
 libtool: definition of this LT_INIT comes from an older release.&lt;br /&gt;
 libtool: You should recreate aclocal.m4 with macros from libtool 2.2.6&lt;br /&gt;
 libtool: and run autoconf again.&lt;br /&gt;
&lt;br /&gt;
Your system uses a different version of libtool. Run:&lt;br /&gt;
&lt;br /&gt;
  libtoolize --ltdl -c -f&lt;br /&gt;
&lt;br /&gt;
and then start from the autoreconf step again.&lt;br /&gt;
&lt;br /&gt;
If you should get the following error try to fix it with one of [http://groups.google.com/group/open-lighting/msg/72060f6327d30df6 two available solutions]:&lt;br /&gt;
&lt;br /&gt;
 Rpc.pb.cc: In copy constructor 'ola::rpc::RpcMessage::RpcMessage(const ola::rpc::RpcMessage&amp;amp;)': &lt;br /&gt;
 Rpc.pb.cc:143: error: base class 'class google::protobuf::Message' should be explicitly initialized in the copy constructor &lt;br /&gt;
&lt;br /&gt;
You should be able to prevent this by [http://groups.google.com/group/open-lighting/msg/c6d86d03dd74ed5b editing &amp;lt;code&amp;gt;./src/Makefile.am&amp;lt;/code&amp;gt;], removing &amp;lt;code&amp;gt;-Werror&amp;lt;/code&amp;gt; and then start from the autoreconfig step again.&lt;br /&gt;
&lt;br /&gt;
=Optional=&lt;br /&gt;
&lt;br /&gt;
==Doxygen Documentation==&lt;br /&gt;
There is also an option to build the doxygen documentation! To do so you will need to install [http://www.stack.nl/~dimitri/doxygen/manual/install.html doxygen].&lt;br /&gt;
&lt;br /&gt;
Once you have installed Doxygen you may need to run ./configure in your ola directory, so that it can generate the correct make file. To build the docs just use:&lt;br /&gt;
&lt;br /&gt;
  make doxygen-doc&lt;br /&gt;
&lt;br /&gt;
You'll have to run a webserver to get the experience. A simple way to do this is to navigate to open-lighting/html and run:&lt;br /&gt;
&lt;br /&gt;
  python -m SimpleHTTPServer&lt;br /&gt;
&lt;br /&gt;
This opens a web server at your local IP address on port 8000. I can be accessed through 127.0.0.1:80000 on your local machine as well.&lt;/div&gt;</summary>
		<author><name>Nightrune</name></author>	</entry>

	<entry>
		<id>https://wiki.openlighting.org/index.php?title=OLA_Device_Specific_Configuration&amp;diff=5595</id>
		<title>OLA Device Specific Configuration</title>
		<link rel="alternate" type="text/html" href="https://wiki.openlighting.org/index.php?title=OLA_Device_Specific_Configuration&amp;diff=5595"/>
				<updated>2013-10-29T17:26:19Z</updated>
		
		<summary type="html">&lt;p&gt;Nightrune: /* Linux */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Anyma ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Linux===&lt;br /&gt;
&lt;br /&gt;
You need a [http://www.reactivated.net/writing_udev_rules.html udev rule] like this in /etc/udev/rules.d/10-local.rules&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
# udev rules file for the anyma dmx device&lt;br /&gt;
SUBSYSTEM==&amp;quot;usb|usb_device&amp;quot;, ACTION==&amp;quot;add&amp;quot;, ATTRS{idVendor}==&amp;quot;16c0&amp;quot;, ATTRS{idProduct}==&amp;quot;05dc&amp;quot;, GROUP=&amp;quot;plugdev&amp;quot;&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==ArtNet ==&lt;br /&gt;
&lt;br /&gt;
If you've having problems sending ArtNet data is may be because your receivers don't support ArtNet II and/or send ArtPollReply messages. You can force OLA to always broadcast data by changing ~/.ola/ola-artnet.conf to contain:&lt;br /&gt;
&lt;br /&gt;
  always_broadcast = true&lt;br /&gt;
==Streaming ACN / E1.31==&lt;br /&gt;
&lt;br /&gt;
===All Platforms===&lt;br /&gt;
Some older networking gear only supports an old revision of E1.31 Called Revision 20. To use this older version you need to change a line in olad-131.conf. Change this line&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
revision = 0.46&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
to this line&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
revision = 0.2&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
Only do this if the older gear cannot accept the standardized version of E1.31.&lt;br /&gt;
&lt;br /&gt;
===Linux===&lt;br /&gt;
If you are planning to receive large amounts of multicast traffic 20+, you will need to adjust the maximum amount of igmp memberships.&lt;br /&gt;
Use the following command:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
echo &amp;lt;number_of_memberships&amp;gt; | sudo tee /proc/sys/net/ipv4/igmp_max_memberships&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For example this command sets the maximum number of igmp memberships to 256:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
echo 256 | sudo tee /proc/sys/net/ipv4/igmp_max_memberships&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Eurolite USB DMX512 PRO==&lt;br /&gt;
&lt;br /&gt;
===Linux===&lt;br /&gt;
&lt;br /&gt;
Sometime the cdc_acm kernel module claims the device. If this happens you'll see errors like &amp;quot;Cannot claim device&amp;quot; and/or &amp;quot;another process has device opened for exclusive access&amp;quot;. To avoid this you can remove the module (rmmod). A udev rule like what is used for the Anyma device should also work.&lt;br /&gt;
&lt;br /&gt;
===Mac===&lt;br /&gt;
&lt;br /&gt;
Install the [http://code.google.com/p/open-lighting/downloads/detail?name=euroliteusbshield.dmg&amp;amp;can=2&amp;amp;q=#makechanges KEXT].&lt;br /&gt;
&lt;br /&gt;
== OSC ==&lt;br /&gt;
&lt;br /&gt;
The message types are described in the  [http://opensoundcontrol.org/spec-1_0 OSC Spec] .&lt;br /&gt;
&lt;br /&gt;
=== Receiving DMX ===&lt;br /&gt;
&lt;br /&gt;
The OSC plugin accepts a number of message formats:&lt;br /&gt;
&lt;br /&gt;
{| border=1 cellspacing=&amp;quot;0&amp;quot;&lt;br /&gt;
! Path !! OSC Message Type !! Data !! Comments &lt;br /&gt;
|-&lt;br /&gt;
|| /path || 'b' || Blob of length 1 to 512. || The most efficient way of sending DMX data over OSC.&lt;br /&gt;
|-&lt;br /&gt;
|| /path/N || 'i' || Slot value from 0 to 255 || Update a single slot. N is the slot number from 1 - 512. &lt;br /&gt;
|-&lt;br /&gt;
|| /path/N || 'f' || Slot value from 0.0 to 1.0 || Update a single slot. N is the slot number from 1 - 512. &lt;br /&gt;
|-&lt;br /&gt;
|| /path || 'ii' || Slot number from 0 to 511, slot value from 0 to 255 || Update a single slot.&lt;br /&gt;
|-&lt;br /&gt;
|| /path || 'if' || Slot number from 0 to 511, slot value from 0.0 to 1.0 || Update a single slot.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Sending DMX ===&lt;br /&gt;
&lt;br /&gt;
The following formats are available for sending data:&lt;br /&gt;
&lt;br /&gt;
{| border=1 cellspacing=&amp;quot;0&amp;quot;&lt;br /&gt;
! Config Option !! Path !! OSC Message Type !! Data !! Comments &lt;br /&gt;
|-&lt;br /&gt;
|| blob || /path || 'b' || Blob of length 1 to 512. || The most efficient way of sending DMX data over OSC.&lt;br /&gt;
|-&lt;br /&gt;
|| float_array || /path || N * 'f' || Slot values from 0.0 to 1.0 ||  Not quite as efficient as the blob type.&lt;br /&gt;
|-&lt;br /&gt;
|| int_array || /path || N * 'i' || Slot values from 0 to 255 ||  Not quite as efficient as the blob type.&lt;br /&gt;
|-&lt;br /&gt;
|| individual_float || /path/N || 'f' || Slot value from 0.0 to 1.0 || N is the slot number from 1 - 512.  Results in a lot of messages being sent, avoid using this. &lt;br /&gt;
|-&lt;br /&gt;
|| individual_int || /path/N || 'i' || Slot value from 0 to 255 || N is the slot number from 1 - 512. Results in a lot of messages being sent, avoid using this. &lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Open DMX USB / FTDI RS485 ==&lt;br /&gt;
&lt;br /&gt;
There are two options, the 'Open DMX' plugin that requires the kernel module and the native FTDI driver.&lt;br /&gt;
&lt;br /&gt;
The Open DMX Plugin requires the dmx_usb kernel module, which means it's Linux only. The FTDI driver can be used on either Mac or Linux.&lt;br /&gt;
&lt;br /&gt;
=== Linux, Open DMX Kernel Module ===&lt;br /&gt;
&lt;br /&gt;
Make sure the opendmx plugin is enabled.&lt;br /&gt;
Make sure the dmx_usb kernel module is loaded. &lt;br /&gt;
&lt;br /&gt;
===Mac FTDI ===&lt;br /&gt;
&lt;br /&gt;
You must have libftdi-dev installed before you run ./configure.  Otherwise the FTDI DMX plugin won't show up in the list of OLA plugins. &lt;br /&gt;
&lt;br /&gt;
Enable the FTDI driver (ola-ftdidmx ) and disable the USB Serial and Open DMX drivers (ola-usbserial.conf &amp;amp;  ola-opendmx.conf) &lt;br /&gt;
&lt;br /&gt;
=== Linux, FTDI ===&lt;br /&gt;
&lt;br /&gt;
Same as Mac, but you also need to make sure that you add the following udev rule:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
# udev rules for ftdi devices&lt;br /&gt;
SUBSYSTEM==&amp;quot;usb|usb_device&amp;quot;, ACTION==&amp;quot;add&amp;quot;, ATTRS{idVendor}==&amp;quot;0403&amp;quot;, ATTRS{idProduct}==&amp;quot;6001&amp;quot;, GROUP=&amp;quot;plugdev&amp;quot;&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== SPI ==&lt;br /&gt;
&lt;br /&gt;
This plugin is designed for the Raspberry Pi. It may work on other hardware, but that's up to you. For instructions on the hardware side of things see [[OLA LED Pixels]].&lt;br /&gt;
&lt;br /&gt;
Enable the spi-bcm2708 module, by editing /etc/modprobe.d/raspi-blacklist.conf and commenting out the &amp;quot;blacklist spi-bcm2708&amp;quot; line. The file should look something like this:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
# blacklist spi and i2c by default (many users don't need them)&lt;br /&gt;
&lt;br /&gt;
#blacklist spi-bcm2708&lt;br /&gt;
blacklist i2c-bcm2708&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
To allow non-root access, add the following to /etc/udev/rules.d/99-spi.rules&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
SUBSYSTEM==&amp;quot;spidev&amp;quot;, MODE=&amp;quot;0666&amp;quot;&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==StageProfi==&lt;br /&gt;
&lt;br /&gt;
This comes in two flavors, a USB model and an Ethernet/IP model.&lt;br /&gt;
&lt;br /&gt;
  device = /dev/ttyUSB0&lt;br /&gt;
  device = 192.168.1.250&lt;br /&gt;
&lt;br /&gt;
==USB Pro==&lt;br /&gt;
&lt;br /&gt;
===Mac===&lt;br /&gt;
&lt;br /&gt;
Make sure you install the drives: http://www.ftdichip.com/Drivers/VCP.htm&lt;br /&gt;
&lt;br /&gt;
After a restart run:&lt;br /&gt;
&lt;br /&gt;
  ls /dev/cu.usbserial-*&lt;br /&gt;
&lt;br /&gt;
Make sure your ~/.ola/ola-usbpro.conf file matches the path above: &lt;br /&gt;
&lt;br /&gt;
  device_dir = /dev&lt;br /&gt;
  device_prefix = ttyUSB&lt;br /&gt;
  device_prefix = cu.usbserial-&lt;br /&gt;
&lt;br /&gt;
i.e. Look for devices at /dev/ttyUSB*  , /dev/cu.usbserial-*&lt;br /&gt;
&lt;br /&gt;
OLA also comes with a tool to update the firmware on a USB Pro:&lt;br /&gt;
&lt;br /&gt;
  ./tools/usbpro_firmware -d /dev/cu.usbserial-0000101D -f &amp;lt;firmware_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==USBDMX2==&lt;br /&gt;
&lt;br /&gt;
===Linux===&lt;br /&gt;
&lt;br /&gt;
You need a [http://www.reactivated.net/writing_udev_rules.html udev rule] like this in /etc/udev/rules.d/10-local.rules&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
# udev rules file for the usbdmx2 dmx device&lt;br /&gt;
SUBSYSTEM==&amp;quot;usb|usb_device&amp;quot;, ACTION==&amp;quot;add&amp;quot;, ATTRS{idVendor}==&amp;quot;0962&amp;quot;, GROUP=&amp;quot;plugdev&amp;quot;&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
There is an issue where the device isn't detected correctly the first time. You may need to restart OLA once the DMX Transmit led comes on.&lt;br /&gt;
&lt;br /&gt;
===Mac===&lt;br /&gt;
&lt;br /&gt;
There is an issue where the device isn't detected correctly the first time. You may need to restart OLA once the DMX Transmit led comes on.&lt;br /&gt;
&lt;br /&gt;
==Velleman VM166 / K8062==&lt;br /&gt;
&lt;br /&gt;
===Mac===&lt;br /&gt;
&lt;br /&gt;
If you're installed from source you'll need the codeless KEXT which is available [http://code.google.com/p/open-lighting/downloads/detail?name=libdmxusbshield.dmg here]. If you installed OLA from the mac binary package this is already included.&lt;br /&gt;
&lt;br /&gt;
===Linux===&lt;br /&gt;
&lt;br /&gt;
You need a [http://www.reactivated.net/writing_udev_rules.html udev rule] like this in /etc/udev/rules.d/10-local.rules&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
# udev rules file for the velleman dmx device&lt;br /&gt;
SUBSYSTEM==&amp;quot;usb|usb_device&amp;quot;, ACTION==&amp;quot;add&amp;quot;, ATTRS{idVendor}==&amp;quot;10cf&amp;quot;, ATTRS{idProduct}==&amp;quot;8062&amp;quot;, GROUP=&amp;quot;plugdev&amp;quot;&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Then make sure the user olad runs as is a member of plugdev.&lt;br /&gt;
&lt;br /&gt;
==KarateLight, KarateDMX==&lt;br /&gt;
&lt;br /&gt;
===Linux===&lt;br /&gt;
&lt;br /&gt;
You need a [http://www.reactivated.net/writing_udev_rules.html udev rule] like this in /etc/udev/rules.d/81-karate.rules&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
# udev rules file for the karate-device&lt;br /&gt;
KERNEL==&amp;quot;ttyACM?&amp;quot;, ATTRS{product}==&amp;quot;DMX2USB simple&amp;quot;, SYMLINK+=&amp;quot;kldmx0&amp;quot;&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
Then make sure the user olad runs as is a member of 'dialout' which is the default group owning ttyACM?.&lt;/div&gt;</summary>
		<author><name>Nightrune</name></author>	</entry>

	<entry>
		<id>https://wiki.openlighting.org/index.php?title=Open_Lighting_Project&amp;diff=5590</id>
		<title>Open Lighting Project</title>
		<link rel="alternate" type="text/html" href="https://wiki.openlighting.org/index.php?title=Open_Lighting_Project&amp;diff=5590"/>
				<updated>2013-10-17T16:29:45Z</updated>
		
		<summary type="html">&lt;p&gt;Nightrune: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;The Open Lighting Project is a multi-faceted effort aimed at accelerating the adoption of new, standardized control protocols, while also providing high quality, reliable, open software for the lighting industry. This site acts as a resource for anyone looking for information about DMX software and the associated control systems, as well as a variety of Open Source and free lighting software.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;table style=&amp;quot;width: 100%; margin:4px 0 0 0; background:none; border-spacing: 5px;&amp;quot;&amp;gt;&lt;br /&gt;
 &amp;lt;tr&amp;gt;&lt;br /&gt;
  &amp;lt;td style=&amp;quot;width:45%; border:1px solid #cedff2; background:#f5faff; vertical-align:top; padding: 4px&amp;quot;&amp;gt;&lt;br /&gt;
    [[Image:OLA-Logo-Fitted-48px.png|right|link=OLA]]&lt;br /&gt;
    &amp;lt;h2 style=&amp;quot;float:left; font-size:120%; padding: .2em; margin:3px; font-weight:bold;&amp;quot;&amp;gt;[[OLA | The Open Lighting Architecture]]&amp;lt;/h2&amp;gt;&lt;br /&gt;
    &amp;lt;div style=&amp;quot;clear: left&amp;quot;&amp;gt;&lt;br /&gt;
The [[OLA | Open Lighting Architecture]] provides a framework for distributing lighting control information. It supports many protocols such as E1.31 (sACN), ArtNet, ShowNet, Pathport, RDM and over a dozen USB devices. It can run as a standalone service, which is useful for converting signals between protocols, or alternatively it can be used as the backend for [[:Category:Controllers | Controller Applications]]. OLA runs on a many different platforms including ARM, which makes it a perfect fit for low cost Ethernet to DMX gateways.&lt;br /&gt;
    &amp;lt;/div&amp;gt;&lt;br /&gt;
  &amp;lt;/td&amp;gt;&lt;br /&gt;
  &amp;lt;td style=&amp;quot;width:45%; border:1px solid #cedff2; background:#f5faff; vertical-align:top; padding: 4px&amp;quot;&amp;gt;&lt;br /&gt;
    [[Image:rdm-logo-small.png|right|link=]]&lt;br /&gt;
    &amp;lt;h2 style=&amp;quot;float:left; font-size:120%; padding: .2em; margin:3px; font-weight:bold;&amp;quot;&amp;gt;[[RDM_Responder_Testing | RDM Responder Tests]]&amp;lt;/h2&amp;gt;&lt;br /&gt;
    &amp;lt;div style=&amp;quot;clear: left&amp;quot;&amp;gt;&lt;br /&gt;
Testing RDM Responder used to involve manually sending commands and verifying the responses. Not any longer! The [[RDM_Responder_Testing | RDM Responder Tests]] automate all of this and provide a detailed breakdown of how well a responder complies with the [[E1.20]] (RDM) standard. This saves time during the product development process and raises the quality of RDM implementations across the industry.&lt;br /&gt;
&lt;br /&gt;
For questions about the RDM Responder tests, email the  [http://groups.google.com/group/rdm-testing RDM Testing List].&lt;br /&gt;
    &amp;lt;/div&amp;gt;&lt;br /&gt;
  &amp;lt;/td&amp;gt;&lt;br /&gt;
 &amp;lt;/tr&amp;gt;&lt;br /&gt;
 &amp;lt;tr&amp;gt;&amp;lt;td colspan=&amp;quot;2&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
 &amp;lt;tr&amp;gt;&lt;br /&gt;
  &amp;lt;td style=&amp;quot;width:45%; border:1px solid #cedff2; background:#f5faff; vertical-align:top; padding: 4px&amp;quot;&amp;gt;&lt;br /&gt;
    [[Image:raspi-logo-small.png|right|link=]]&lt;br /&gt;
    &amp;lt;h2 style=&amp;quot;float:left; font-size:120%; padding: .2em; margin:3px; font-weight:bold;&amp;quot;&amp;gt;[[OLA_Raspberry_Pi | OLA on the Raspberry Pi]]&amp;lt;/h2&amp;gt;&lt;br /&gt;
    &amp;lt;div style=&amp;quot;clear: left&amp;quot;&amp;gt;&lt;br /&gt;
The [http://www.raspberrypi.org/ Raspberry Pi] is one of the most popular platforms for running [[OLA]]. With the addition of a USB to DMX device, one can build a low cost, but fully functional Ethernet gateway. The [[OLA_Raspberry_Pi | OLA on Raspberry Pi]] tutorial has a step by step guide to installing OLA on the Pi.&lt;br /&gt;
    &amp;lt;/div&amp;gt;&lt;br /&gt;
  &amp;lt;/td&amp;gt;&lt;br /&gt;
&lt;br /&gt;
  &amp;lt;td style=&amp;quot;width:45%; border:1px solid #cedff2; background:#f5faff; vertical-align:top; padding: 4px&amp;quot;&amp;gt;&lt;br /&gt;
    [[Image:Robin-1200.png|right|link=]]&lt;br /&gt;
    &amp;lt;h2 style=&amp;quot;float:left; font-size:120%; padding: .2em; margin:3px; font-weight:bold;&amp;quot;&amp;gt;rdm.openlighting.org&amp;lt;/h2&amp;gt;&lt;br /&gt;
    &amp;lt;div style=&amp;quot;clear: left&amp;quot;&amp;gt;&lt;br /&gt;
The http://rdm.openlighting.org site contains an index of RDM-enabled products as well as the specifications for many of the manufacturer specific PIDs. The site has recently been expanded to display the results of the RDM Responder Tests. The data on the site is available free of charge through APIs. &lt;br /&gt;
    &amp;lt;/div&amp;gt;&lt;br /&gt;
  &amp;lt;/td&amp;gt;&lt;br /&gt;
 &amp;lt;/tr&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td colspan=&amp;quot;2&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
 &amp;lt;tr&amp;gt;&lt;br /&gt;
  &amp;lt;td style=&amp;quot;width:45%; border:1px solid #cedff2; background:#f5faff; vertical-align:top; padding: 4px&amp;quot;&amp;gt;&lt;br /&gt;
    [[Image:Email-icon.png|right|link=]]&lt;br /&gt;
    &amp;lt;h2 style=&amp;quot;float:left; font-size:120%; padding: .2em; margin:3px; font-weight:bold;&amp;quot;&amp;gt;Contact / Support&amp;lt;/h2&amp;gt;&lt;br /&gt;
    &amp;lt;div style=&amp;quot;clear: left&amp;quot;&amp;gt;&lt;br /&gt;
Since this is an Open Source project, there is no commercial support for our products at this time. There are a number of ways of reaching the community though:&lt;br /&gt;
&lt;br /&gt;
* Primary User &amp;amp; Developer Discussion [http://groups.google.com/group/open-lighting Open Lighting Discuss] (typically a few messages per day).&lt;br /&gt;
* Announcements are posted to [http://groups.google.com/group/open-lighting-announce Open Lighting Announce] (low volume, typically 1-2 per month)&lt;br /&gt;
* RDM Testing Discussion [http://groups.google.com/group/rdm-testing RDM Testing].&lt;br /&gt;
* IRC #openlighting on freenode.net (or [http://webchat.freenode.net/?channels=openlighting webchat])&lt;br /&gt;
There is also an [https://plus.google.com/106460627923808853381 Open Lighting Community] on Google+. This is less OLA centric and more about sharing cool lighting projects people are working on. We also have a cafepress store where you can buy OLA t-shirts, stickers, and a few other random things. Visit [http://www.cafepress.com/openlighting Open Lighting at Cafepress]! Prices may change in the future. &lt;br /&gt;
    &amp;lt;/div&amp;gt;&lt;br /&gt;
  &amp;lt;/td&amp;gt;&lt;br /&gt;
&lt;br /&gt;
  &amp;lt;td style=&amp;quot;width:45%; border:1px solid #cedff2; background:#f5faff; vertical-align:top; padding: 4px&amp;quot;&amp;gt;&lt;br /&gt;
    &amp;lt;h2 style=&amp;quot;float:left; font-size:120%; padding: .2em; margin:3px; font-weight:bold;&amp;quot;&amp;gt;Other Projects&amp;lt;/h2&amp;gt;&lt;br /&gt;
    &amp;lt;div style=&amp;quot;clear: left&amp;quot;&amp;gt;&lt;br /&gt;
* [[libartnet]]. The library that started it all, libartnet is an [[ArtNet]] implementation for Mac, Linux, Windows &amp;amp; iPhone.&lt;br /&gt;
* [[Logic RDM Sniffer]] - Use a [http://saleae.com/logic Saleae Logic] device as a RDM analyzer. &lt;br /&gt;
* [[Arduino RGB Mixer]], open source firmware for Arduinos, so that they can be used as a simple RGB Color Mixer. Now with RDM support!&lt;br /&gt;
* [[OLA_DMX_Trigger | DMX Trigger]], this can execute command line programs based on DMX values. It's useful for building DMX controlled media players.&lt;br /&gt;
* [[E1.33 SLP SA Tests]], similar to the RDM Responder Tests, this performs tests against a RDMNet Device's SLP implementation.&lt;br /&gt;
* [[OLA LED Pixels]], drive pixel strings using OLA&lt;br /&gt;
    &amp;lt;/div&amp;gt;&lt;br /&gt;
  &amp;lt;/td&amp;gt;&lt;br /&gt;
 &amp;lt;/tr&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td colspan=&amp;quot;2&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
 &amp;lt;tr&amp;gt;&lt;br /&gt;
  &amp;lt;td style=&amp;quot;width:45%; border:1px solid #cedff2; background:#f5faff; vertical-align:top; padding: 4px&amp;quot;&amp;gt;&lt;br /&gt;
    &amp;lt;h2 style=&amp;quot;float:left; font-size:120%; padding: .2em; margin:3px; font-weight:bold;&amp;quot;&amp;gt;Project Supporters&amp;lt;/h2&amp;gt;&lt;br /&gt;
    &amp;lt;div style=&amp;quot;clear: left&amp;quot;&amp;gt;&lt;br /&gt;
Many individuals &amp;amp; organizations have supported the project over the years. We're grateful to all of them.&lt;br /&gt;
&lt;br /&gt;
* [http://www.anyma.ch Anyma], provided a [[Anyma_uDMX|uDMX]]&lt;br /&gt;
* [[Artistic Licence]], provided a [[Net-Lynx]] &amp;amp; Down-Lynx for Art-Net / RDM testing and a [[Rail-Tran]] to test [[RDM]] support&lt;br /&gt;
* Andrew Frazer, who sponsored the development of ola_trigger with a [[RDM USB Pro]] &lt;br /&gt;
* [http://www.creativelighting.com.au/ Creative Lighting], provided a [[SLAMMO XC-1]] &amp;amp; [[ADDICT]] for [[RDM]] testing.&lt;br /&gt;
* [[Enttec]], provided a [[DMX USB Pro]]&lt;br /&gt;
* Eric Johnson, for hosting the server used to test &amp;amp; debug much of the RDM code.&lt;br /&gt;
* Florian from eventa.ag who donated a [[StageProfi]] and a [[USBDMX2]]&lt;br /&gt;
* [http://www.goddarddesign.com/ Goddard Design], who made available a  [[MiniDMXter]]&lt;br /&gt;
* Jason Kyle from [http://www.DMXking.com DMXKing.com] provided a [[DMXking USB DMX512-A]]&lt;br /&gt;
* [[JESE]], provided a [[DMX-TRI]] &amp;amp;  [[RDM-TRI]] &amp;amp; Tempest Enclosure to test the RDM implementation. &lt;br /&gt;
* [http://www.ljusdesign.se LjusDesign AB] who donated 7 RDM splitters.&lt;br /&gt;
* [http://www.lumenradio.com/ LumenRadio] who provided a Nova TX2 RDM, Nova RX RDM and Nova FX units and a Raspberry Pi.&lt;br /&gt;
* [http://www.martin.com Martin Professional A/S] which loaned a Mac 700 for RDM testing &lt;br /&gt;
* [http://www.milinst.co.uk/ Milford Instruments] who sent 3 RDMChips for testing.&lt;br /&gt;
* Peter Kirkup, from [http://www.zero88.com/ Zero 88] who donated a Betapack 3&lt;br /&gt;
* Petr from [[ROBE Lighting]] who loaned a [[Robe Universal Interface]] and [http://www.robe.cz/products/article/robin-600e-spot/ Robin 600]&lt;br /&gt;
* [http://www.sandsys.com/ Sandsys], donated a [http://www.sandsys.com/products/SB-AAA2100.htm SandBox]&lt;br /&gt;
* Shaun Jackman, answered questions about the [[:Category:Pathport|Pathport]] Protocol&lt;br /&gt;
* [http://soundlight.de/ SoundLight] who loaned a 3604PWM-H device&lt;br /&gt;
* [http://www.waapa.ecu.edu.au West Australian Academy of Performing Arts] (WAAPA) for access to a [[Strand Lighting]] console.&lt;br /&gt;
&lt;br /&gt;
    &amp;lt;/div&amp;gt;&lt;br /&gt;
  &amp;lt;/td&amp;gt;&lt;br /&gt;
&lt;br /&gt;
  &amp;lt;td style=&amp;quot;width:45%; border:1px solid #cedff2; background:#f5faff; vertical-align:top; padding: 4px&amp;quot;&amp;gt;&lt;br /&gt;
    &amp;lt;h2 style=&amp;quot;float:left; font-size:120%; padding: .2em; margin:3px; font-weight:bold;&amp;quot;&amp;gt;Get Involved&amp;lt;/h2&amp;gt;&lt;br /&gt;
    &amp;lt;div style=&amp;quot;clear: left&amp;quot;&amp;gt;&lt;br /&gt;
There is plenty of opportunity to get involved. If you would like to help with any of the following (or have your own ideas) then please get in touch with us on the [http://groups.google.com/group/open-lighting Open Lighting Group]&lt;br /&gt;
&lt;br /&gt;
* Technical Writers, the documentation could do with some cleanup.&lt;br /&gt;
* Packagers, we need people to build binary packages for Mac, Debian/Ubuntu and RPM-based distros&lt;br /&gt;
* Windows programmers, are you interested in helping [[Building_OLA_for_Windows| port OLA to Windows]]?  &lt;br /&gt;
* Java programmers, we need someone to write the Java client API [http://code.google.com/p/linux-lighting/issues/detail?id=15 ]&lt;br /&gt;
* Equipment donation, do you own or know of a [[:Category:USB | USB interface]] or RDM device we don't support yet? Consider lending it to us.&lt;br /&gt;
* Web designers, the web UI could do with a facelift.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The programming team behind OLA consists of:&lt;br /&gt;
* Bastien Andrès, contributed to the dmx4linux plugin&lt;br /&gt;
* Harry F, for the Eurolite USB Pro code&lt;br /&gt;
* Heikki Junnila, bug fixes for the debian packaging files&lt;br /&gt;
* Laurent  (Renzo), Debian packages, FreeBSD &amp;amp; RDM testing.&lt;br /&gt;
* Masaki Muranaka, various patches&lt;br /&gt;
* Peter Newman, man pages, various patches&lt;br /&gt;
* Nicolas, for the win32 port of libartnet&lt;br /&gt;
* Ravindra Nath Kakarla, RDM Test Server (Part of [http://www.google-melange.com/gsoc/profile/organization/google/gsoc2012/openlighting Google Summer of Code 2012] ).&lt;br /&gt;
* Rowan Maclachlan (hippy) for various changes&lt;br /&gt;
* Joshua Moyerman, various changes.&lt;br /&gt;
* Carsten Presser , Karate Light plugin&lt;br /&gt;
* Rui Barreiros for the FTDI plugin&lt;br /&gt;
* Sean Sill, RDM, doxygen comments.&lt;br /&gt;
* Tobi Schäfer, for the MacPort files&lt;br /&gt;
    &amp;lt;/div&amp;gt;&lt;br /&gt;
  &amp;lt;/td&amp;gt;&lt;br /&gt;
 &amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;/table&amp;gt;&lt;br /&gt;
&lt;br /&gt;
__NOTOC__&lt;/div&gt;</summary>
		<author><name>Nightrune</name></author>	</entry>

	<entry>
		<id>https://wiki.openlighting.org/index.php?title=OLA_Device_Specific_Configuration&amp;diff=5580</id>
		<title>OLA Device Specific Configuration</title>
		<link rel="alternate" type="text/html" href="https://wiki.openlighting.org/index.php?title=OLA_Device_Specific_Configuration&amp;diff=5580"/>
				<updated>2013-09-27T15:03:02Z</updated>
		
		<summary type="html">&lt;p&gt;Nightrune: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Anyma ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Linux===&lt;br /&gt;
&lt;br /&gt;
You need a [http://www.reactivated.net/writing_udev_rules.html udev rule] like this in /etc/udev/rules.d/10-local.rules&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
# udev rules file for the anyma dmx device&lt;br /&gt;
SUBSYSTEM==&amp;quot;usb|usb_device&amp;quot;, ACTION==&amp;quot;add&amp;quot;, ATTRS{idVendor}==&amp;quot;16c0&amp;quot;, ATTRS{idProduct}==&amp;quot;05dc&amp;quot;, GROUP=&amp;quot;plugdev&amp;quot;&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==ArtNet ==&lt;br /&gt;
&lt;br /&gt;
If you've having problems sending ArtNet data is may be because your receivers don't support ArtNet II and/or send ArtPollReply messages. You can force OLA to always broadcast data by changing ~/.ola/ola-artnet.conf to contain:&lt;br /&gt;
&lt;br /&gt;
  always_broadcast = true&lt;br /&gt;
==Streaming ACN / E1.31==&lt;br /&gt;
&lt;br /&gt;
===Linux===&lt;br /&gt;
If you are planning to receive large amounts of multicast traffic 20+, you will need to adjust the maximum amount of igmp memberships.&lt;br /&gt;
Use the following command:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
echo &amp;lt;number_of_memberships&amp;gt; | sudo tee /proc/sys/net/ipv4/igmp_max_memberships&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For example this command sets the maximum number of igmp memberships to 256:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
echo 256 | sudo tee /proc/sys/net/ipv4/igmp_max_memberships&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Eurolite USB DMX512 PRO==&lt;br /&gt;
&lt;br /&gt;
===Linux===&lt;br /&gt;
&lt;br /&gt;
Sometime the cdc_acm kernel module claims the device. If this happens you'll see errors like &amp;quot;Cannot claim device&amp;quot; and/or &amp;quot;another process has device opened for exclusive access&amp;quot;. To avoid this you can remove the module (rmmod). A udev rule like what is used for the Anyma device should also work.&lt;br /&gt;
&lt;br /&gt;
===Mac===&lt;br /&gt;
&lt;br /&gt;
Install the [http://code.google.com/p/open-lighting/downloads/detail?name=euroliteusbshield.dmg&amp;amp;can=2&amp;amp;q=#makechanges KEXT].&lt;br /&gt;
&lt;br /&gt;
== OSC ==&lt;br /&gt;
&lt;br /&gt;
The message types are described in the  [http://opensoundcontrol.org/spec-1_0 OSC Spec] .&lt;br /&gt;
&lt;br /&gt;
=== Receiving DMX ===&lt;br /&gt;
&lt;br /&gt;
The OSC plugin accepts a number of message formats:&lt;br /&gt;
&lt;br /&gt;
{| border=1 cellspacing=&amp;quot;0&amp;quot;&lt;br /&gt;
! Path !! OSC Message Type !! Data !! Comments &lt;br /&gt;
|-&lt;br /&gt;
|| /path || 'b' || Blob of length 1 to 512. || The most efficient way of sending DMX data over OSC.&lt;br /&gt;
|-&lt;br /&gt;
|| /path/N || 'i' || Slot value from 0 to 255 || Update a single slot. N is the slot number from 1 - 512. &lt;br /&gt;
|-&lt;br /&gt;
|| /path/N || 'f' || Slot value from 0.0 to 1.0 || Update a single slot. N is the slot number from 1 - 512. &lt;br /&gt;
|-&lt;br /&gt;
|| /path || 'ii' || Slot number from 0 to 511, slot value from 0 to 255 || Update a single slot.&lt;br /&gt;
|-&lt;br /&gt;
|| /path || 'if' || Slot number from 0 to 511, slot value from 0.0 to 1.0 || Update a single slot.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Sending DMX ===&lt;br /&gt;
&lt;br /&gt;
The following formats are available for sending data:&lt;br /&gt;
&lt;br /&gt;
{| border=1 cellspacing=&amp;quot;0&amp;quot;&lt;br /&gt;
! Config Option !! Path !! OSC Message Type !! Data !! Comments &lt;br /&gt;
|-&lt;br /&gt;
|| blob || /path || 'b' || Blob of length 1 to 512. || The most efficient way of sending DMX data over OSC.&lt;br /&gt;
|-&lt;br /&gt;
|| float_array || /path || N * 'f' || Slot values from 0.0 to 1.0 ||  Not quite as efficient as the blob type.&lt;br /&gt;
|-&lt;br /&gt;
|| int_array || /path || N * 'i' || Slot values from 0 to 255 ||  Not quite as efficient as the blob type.&lt;br /&gt;
|-&lt;br /&gt;
|| individual_float || /path/N || 'f' || Slot value from 0.0 to 1.0 || N is the slot number from 1 - 512.  Results in a lot of messages being sent, avoid using this. &lt;br /&gt;
|-&lt;br /&gt;
|| individual_int || /path/N || 'i' || Slot value from 0 to 255 || N is the slot number from 1 - 512. Results in a lot of messages being sent, avoid using this. &lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Open DMX USB / FTDI RS485 ==&lt;br /&gt;
&lt;br /&gt;
There are two options, the 'Open DMX' plugin that requires the kernel module and the native FTDI driver.&lt;br /&gt;
&lt;br /&gt;
The Open DMX Plugin requires the dmx_usb kernel module, which means it's Linux only. The FTDI driver can be used on either Mac or Linux.&lt;br /&gt;
&lt;br /&gt;
=== Linux, Open DMX Kernel Module ===&lt;br /&gt;
&lt;br /&gt;
Make sure the opendmx plugin is enabled.&lt;br /&gt;
Make sure the dmx_usb kernel module is loaded. &lt;br /&gt;
&lt;br /&gt;
===Mac FTDI ===&lt;br /&gt;
&lt;br /&gt;
You must have libftdi-dev installed before you run ./configure.  Otherwise the FTDI DMX plugin won't show up in the list of OLA plugins. &lt;br /&gt;
&lt;br /&gt;
Enable the FTDI driver (ola-ftdidmx ) and disable the USB Serial and Open DMX drivers (ola-usbserial.conf &amp;amp;  ola-opendmx.conf) &lt;br /&gt;
&lt;br /&gt;
=== Linux, FTDI ===&lt;br /&gt;
&lt;br /&gt;
Same as Mac, but you also need to make sure that you add the following udev rule:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
# udev rules for ftdi devices&lt;br /&gt;
SUBSYSTEM==&amp;quot;usb|usb_device&amp;quot;, ACTION==&amp;quot;add&amp;quot;, ATTRS{idVendor}==&amp;quot;0403&amp;quot;, ATTRS{idProduct}==&amp;quot;6001&amp;quot;, GROUP=&amp;quot;plugdev&amp;quot;&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== SPI ==&lt;br /&gt;
&lt;br /&gt;
This plugin is designed for the Raspberry Pi. It may work on other hardware, but that's up to you. For instructions on the hardware side of things see [[OLA LED Pixels]].&lt;br /&gt;
&lt;br /&gt;
Enable the spi-bcm2708 module, by editing /etc/modprobe.d/raspi-blacklist.conf and commenting out the &amp;quot;blacklist spi-bcm2708&amp;quot; line. The file should look something like this:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
# blacklist spi and i2c by default (many users don't need them)&lt;br /&gt;
&lt;br /&gt;
#blacklist spi-bcm2708&lt;br /&gt;
blacklist i2c-bcm2708&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
To allow non-root access, add the following to /etc/udev/rules.d/99-spi.rules&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
SUBSYSTEM==&amp;quot;spidev&amp;quot;, MODE=&amp;quot;0666&amp;quot;&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==StageProfi==&lt;br /&gt;
&lt;br /&gt;
This comes in two flavors, a USB model and an Ethernet/IP model.&lt;br /&gt;
&lt;br /&gt;
  device = /dev/ttyUSB0&lt;br /&gt;
  device = 192.168.1.250&lt;br /&gt;
&lt;br /&gt;
==USB Pro==&lt;br /&gt;
&lt;br /&gt;
===Mac===&lt;br /&gt;
&lt;br /&gt;
Make sure you install the drives: http://www.ftdichip.com/Drivers/VCP.htm&lt;br /&gt;
&lt;br /&gt;
After a restart run:&lt;br /&gt;
&lt;br /&gt;
  ls /dev/cu.usbserial-*&lt;br /&gt;
&lt;br /&gt;
Make sure your ~/.ola/ola-usbpro.conf file matches the path above: &lt;br /&gt;
&lt;br /&gt;
  device_dir = /dev&lt;br /&gt;
  device_prefix = ttyUSB&lt;br /&gt;
  device_prefix = cu.usbserial-&lt;br /&gt;
&lt;br /&gt;
i.e. Look for devices at /dev/ttyUSB*  , /dev/cu.usbserial-*&lt;br /&gt;
&lt;br /&gt;
OLA also comes with a tool to update the firmware on a USB Pro:&lt;br /&gt;
&lt;br /&gt;
  ./tools/usbpro_firmware -d /dev/cu.usbserial-0000101D -f &amp;lt;firmware_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==USBDMX2==&lt;br /&gt;
&lt;br /&gt;
===Linux===&lt;br /&gt;
&lt;br /&gt;
You need a [http://www.reactivated.net/writing_udev_rules.html udev rule] like this in /etc/udev/rules.d/10-local.rules&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
# udev rules file for the usbdmx2 dmx device&lt;br /&gt;
SUBSYSTEM==&amp;quot;usb|usb_device&amp;quot;, ACTION==&amp;quot;add&amp;quot;, ATTRS{idVendor}==&amp;quot;0962&amp;quot;, GROUP=&amp;quot;plugdev&amp;quot;&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
There is an issue where the device isn't detected correctly the first time. You may need to restart OLA once the DMX Transmit led comes on.&lt;br /&gt;
&lt;br /&gt;
===Mac===&lt;br /&gt;
&lt;br /&gt;
There is an issue where the device isn't detected correctly the first time. You may need to restart OLA once the DMX Transmit led comes on.&lt;br /&gt;
&lt;br /&gt;
==Velleman VM166 / K8062==&lt;br /&gt;
&lt;br /&gt;
===Mac===&lt;br /&gt;
&lt;br /&gt;
If you're installed from source you'll need the codeless KEXT which is available [http://code.google.com/p/open-lighting/downloads/detail?name=libdmxusbshield.dmg here]. If you installed OLA from the mac binary package this is already included.&lt;br /&gt;
&lt;br /&gt;
===Linux===&lt;br /&gt;
&lt;br /&gt;
You need a [http://www.reactivated.net/writing_udev_rules.html udev rule] like this in /etc/udev/rules.d/10-local.rules&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
# udev rules file for the velleman dmx device&lt;br /&gt;
SUBSYSTEM==&amp;quot;usb|usb_device&amp;quot;, ACTION==&amp;quot;add&amp;quot;, ATTRS{idVendor}==&amp;quot;10cf&amp;quot;, ATTRS{idProduct}==&amp;quot;8062&amp;quot;, GROUP=&amp;quot;plugdev&amp;quot;&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Then make sure the user olad runs as is a member of plugdev.&lt;br /&gt;
&lt;br /&gt;
==KarateLight, KarateDMX==&lt;br /&gt;
&lt;br /&gt;
===Linux===&lt;br /&gt;
&lt;br /&gt;
You need a [http://www.reactivated.net/writing_udev_rules.html udev rule] like this in /etc/udev/rules.d/81-karate.rules&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
# udev rules file for the karate-device&lt;br /&gt;
KERNEL==&amp;quot;ttyACM?&amp;quot;, ATTRS{product}==&amp;quot;DMX2USB simple&amp;quot;, SYMLINK+=&amp;quot;kldmx0&amp;quot;&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
Then make sure the user olad runs as is a member of 'dialout' which is the default group owning ttyACM?.&lt;/div&gt;</summary>
		<author><name>Nightrune</name></author>	</entry>

	<entry>
		<id>https://wiki.openlighting.org/index.php?title=Logic_RDM_Sniffer&amp;diff=5569</id>
		<title>Logic RDM Sniffer</title>
		<link rel="alternate" type="text/html" href="https://wiki.openlighting.org/index.php?title=Logic_RDM_Sniffer&amp;diff=5569"/>
				<updated>2013-09-16T15:57:12Z</updated>
		
		<summary type="html">&lt;p&gt;Nightrune: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Image:Saleae-logic.jpg|thumb|200px|right|Saleae Logic]]&lt;br /&gt;
[[Image:Logic-sniffer.jpg|thumb|200px|right|The Logic as a 2 line DMX/RDM sniffer]]&lt;br /&gt;
&lt;br /&gt;
The [http://www.saleae.com/logic Saleae Logic] makes an excellent [[DMX]] / [[RDM]] sniffer.  With the Logic and a small amount of hardware you can build a sniffer for a fraction of the price of commercial units.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Parts ==&lt;br /&gt;
* A Logic or Logic 16, but see the note below.&lt;br /&gt;
* 485 driver circuit&lt;br /&gt;
* XLR connectors.&lt;br /&gt;
&lt;br /&gt;
== Electrical ==&lt;br /&gt;
&lt;br /&gt;
You need some hardware to convert from the differential 485 levels to a signal which the logic can understand.&lt;br /&gt;
&lt;br /&gt;
At the basic level you only need an RS-485 receiver like the Maxim MAX485 or Linear Technology LT1785 to translate from the DMX/RDM differential levels to a TTL level that the Saleae Logic understands.&lt;br /&gt;
[[File:RDMSnifferSchematic.jpg|thumb|center|400px|alt=Example Circuit]]&lt;br /&gt;
&lt;br /&gt;
Connecting this circuit to the Logic is fairly simple. Power the board with a MicroUSB Cable or from the +5V, and COM pins on the TTL connector. Then attach the Logic's grey Ground wire to the COM pin on the sniffer circuit, pull the DIR pin low to put the board in RX mode and connect your Logic's channel 1 (generally it's the black cable) to the RX pin. Finally Connect a DXM/RDM source to the board and make sure the green LED is flickering to show data is receiving on the TTL side.&lt;br /&gt;
&lt;br /&gt;
For more information check [[RDM Sniffer Board]]&lt;br /&gt;
== Software ==&lt;br /&gt;
&lt;br /&gt;
=== Saleae Logic ===&lt;br /&gt;
&lt;br /&gt;
[[Image:Saleae-dmx.png|thumb|200px|right|The Logic App decoding DMX]]&lt;br /&gt;
&lt;br /&gt;
Saleae provides the [http://www.saleae.com/downloads Logic App] which works on Windows, Mac and Linux. The application has a plugin to decode DMX, but it doesn't understand RDM data. The tool is best for analyzing the signal timing rather than the high level messages.&lt;br /&gt;
&lt;br /&gt;
=== OLA Sniffer ===&lt;br /&gt;
&lt;br /&gt;
OLA has a text-based DMX/RDM sniffer that works with the Logic (it could easily be extended to work with the Logic 16). It can be found in [http://code.google.com/p/open-lighting/source/browse/#git%2Ftools%2Flogic tools/logic] directory of the OLA sources.&lt;br /&gt;
&lt;br /&gt;
Limitations:&lt;br /&gt;
* the sniffer doesn't understand DUB responses yet since it looks for breaks.&lt;br /&gt;
* it may struggle with signal timings that are at the edge of the E1.11 standard. If you experience problems with the sniffer please email the [http://groups.google.com/forum/#!forum/open-lighting Open Lighting Mailing List]&lt;/div&gt;</summary>
		<author><name>Nightrune</name></author>	</entry>

	<entry>
		<id>https://wiki.openlighting.org/index.php?title=RDM_Sniffer_Board&amp;diff=5568</id>
		<title>RDM Sniffer Board</title>
		<link rel="alternate" type="text/html" href="https://wiki.openlighting.org/index.php?title=RDM_Sniffer_Board&amp;diff=5568"/>
				<updated>2013-09-16T15:55:20Z</updated>
		
		<summary type="html">&lt;p&gt;Nightrune: Created page with &amp;quot;== About ==  Here is a typical RDM Sniffer board that is available to purchase from SeanSill for $65 without shipping. You can contact him either through [https://groups.googl...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== About ==&lt;br /&gt;
&lt;br /&gt;
Here is a typical RDM Sniffer board that is available to purchase from SeanSill for $65 without shipping. You can contact him either through [https://groups.google.com/d/topic/open-lighting/cKjzIK-tLyI/discussion RDM Sniffer Board] or through our [http://webchat.freenode.net/?channels=openlighting IRC Webchat] &lt;br /&gt;
&lt;br /&gt;
[[File:RDMSnifferSideView.jpg|thumbnail|center|600px]]&lt;br /&gt;
&lt;br /&gt;
== Specifications ==&lt;br /&gt;
&lt;br /&gt;
The board uses a MicroUSB cable for power or you can supply power on the +5V, COM pins on the white MTA connector. Power is 5V at a maximum of .25 A. It also has 1000V optical isolation to keep your Saleae Logic safe from transients on the RS485 side. The transceiver that is used is the LT1785 which has +/- 60V protection on the DMX+ and DMX- pins. Meaning it won't keel over if someone manages to connect +48V to your DMX line.&lt;br /&gt;
&lt;br /&gt;
The board can also work as a transmitter if you want a quick way to send DMX from a Beagle Bone/Ardunio or anything with a TTL serial port.&lt;br /&gt;
&lt;br /&gt;
== Schematic == &lt;br /&gt;
&lt;br /&gt;
[[File:RDMSnifferSchematic.jpg|thumb|center|400px|alt=Example Circuit]]&lt;/div&gt;</summary>
		<author><name>Nightrune</name></author>	</entry>

	<entry>
		<id>https://wiki.openlighting.org/index.php?title=File:RDMSnifferSideView.jpg&amp;diff=5567</id>
		<title>File:RDMSnifferSideView.jpg</title>
		<link rel="alternate" type="text/html" href="https://wiki.openlighting.org/index.php?title=File:RDMSnifferSideView.jpg&amp;diff=5567"/>
				<updated>2013-09-16T15:31:39Z</updated>
		
		<summary type="html">&lt;p&gt;Nightrune: Side view of the RDM Sniffer Board.&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Side view of the RDM Sniffer Board.&lt;/div&gt;</summary>
		<author><name>Nightrune</name></author>	</entry>

	<entry>
		<id>https://wiki.openlighting.org/index.php?title=RDM_with_OLA&amp;diff=5566</id>
		<title>RDM with OLA</title>
		<link rel="alternate" type="text/html" href="https://wiki.openlighting.org/index.php?title=RDM_with_OLA&amp;diff=5566"/>
				<updated>2013-09-16T15:17:23Z</updated>
		
		<summary type="html">&lt;p&gt;Nightrune: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[RDM]] devices can be configured through the web interface (only partially complete) or from the command line. Even if you don't have any RDM devices you can still experiment using the fake RDM device created by the Dummy Plugin.&lt;br /&gt;
&lt;br /&gt;
To follow these examples, patch the Dummy Port to universe 1.&lt;br /&gt;
&lt;br /&gt;
== Device Discovery  ==&lt;br /&gt;
&lt;br /&gt;
Each RDM device has a unique ID (UID) made up of a two byte manufacturer ID and a four byte device ID. The ''ola_rdm_discovery'' tool displays the UIDs found for each universe.&lt;br /&gt;
 &lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
$ ola_rdm_discover  -u 1&lt;br /&gt;
7a70:ffffff00&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
A single device should be found with a manufacturer ID of 7a70 (Open Lighting) and a device ID of ffffff00 (the dummy device).&lt;br /&gt;
&lt;br /&gt;
Passing the -f option will force the discovery algorithm to be run for the particular universe. This won't produce any output unless an error occurs.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
$ ola_rdm_discover  -u 1 -f&lt;br /&gt;
&amp;lt;/pre&amp;gt; &lt;br /&gt;
&lt;br /&gt;
== Device Configuration ==&lt;br /&gt;
&lt;br /&gt;
Now that a device has been found, we can query it to find the parameters it supports. Each parameter is assigned a two byte identifier known as a PID. The  ''ola_rdm_get'' and ''ola_rdm_set'' commands are used to read / write the values of parameters.  The first thing to do is to view a list of all known parameters:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
$ ola_rdm_get  --list_pids&lt;br /&gt;
boot_software_version_id&lt;br /&gt;
boot_software_version_label&lt;br /&gt;
capture_preset&lt;br /&gt;
clear_status_id&lt;br /&gt;
comms_status&lt;br /&gt;
default_slot_value&lt;br /&gt;
device_hours&lt;br /&gt;
device_info&lt;br /&gt;
...&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This doesn't query the RDM device at all, it simply lists out the names of standard parameters. To see which particular parameters a device supports use:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
$ ola_rdm_get  --universe 1 --uid 7a70:ffffff00 supported_parameters&lt;br /&gt;
Supported Parameters&lt;br /&gt;
  0x50 (supported_parameters)&lt;br /&gt;
  0x60 (device_info)&lt;br /&gt;
  0x80 (device_model_description)&lt;br /&gt;
  0x81 (manufacturer_label)&lt;br /&gt;
  0x82 (device_label)&lt;br /&gt;
  0xc0 (software_version_label)&lt;br /&gt;
  0xf0 (dmx_start_address)&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
One of the most useful parameters is device_info:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
$ ola_rdm_get  --universe 1 --uid 7a70:ffffff00 device_info&lt;br /&gt;
Device Info&lt;br /&gt;
RDM Protocol Version: 1.0&lt;br /&gt;
Device Model: 0x1&lt;br /&gt;
Product Category: other&lt;br /&gt;
Software Version: 0x1&lt;br /&gt;
DMX Footprint: 10&lt;br /&gt;
DMX Personality: 1 / 1&lt;br /&gt;
DMX Start Address: 1&lt;br /&gt;
# of Subdevices: 0&lt;br /&gt;
Sensor Count: 0&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Here we see some general information about the device including the DMX start address and the # of DMX channels used (DMX Footprint). We can also get the DMX start address by using the dmx_start_address parameter directly:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
$ ola_rdm_get  --universe 1 --uid 7a70:ffffff00 dmx_start_address &lt;br /&gt;
DMX Start Address: 1&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
To set the start address, the  ''ola_rdm_set'' program is used:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
$ ola_rdm_set  --universe 1 --uid 7a70:ffffff00 dmx_start_address  10&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
No output is displayed unless the request failed. Now we can check that the set worked:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
$ ola_rdm_get  --universe 1 --uid 7a70:ffffff00 dmx_start_address &lt;br /&gt;
DMX Start Address: 10&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Finally, the full list of options for ''ola_rdm_get'' and ''ola_rdm_set'' can be found by running with --help:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
  -d, --sub_device &amp;lt;device&amp;gt; target a particular sub device (default is 0)&lt;br /&gt;
  -h, --help                               display this help message and exit.&lt;br /&gt;
  -l, --list_pids                         display a list of pids&lt;br /&gt;
  -u, --universe &amp;lt;universe&amp;gt;  universe number.&lt;br /&gt;
  --uid &amp;lt;uid&amp;gt;                            the UID of the device to control.&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Manufacturer Specific PIDs==&lt;br /&gt;
The dummy devices also support one [[Open Lighting PIDs|manufacturer specific PID]], to allow you to experiment with those features, which returns the current OLA version.&lt;br /&gt;
&lt;br /&gt;
== RDM With ArtNet ==&lt;br /&gt;
&lt;br /&gt;
If you have a copy of DMXWorkshop, you can experiment with RDM over ArtNet by patching an ArtNet Input Port to the same universe as the Dummy Plugin. You can then discover the Dummy Device using DMXWorkshop and configure it's start address over the LAN.&lt;br /&gt;
&lt;br /&gt;
Note that the design of the RDM-over-ArtNet protocol has a significant limitation, see [[ArtNet, RDM and Packet Interleaving]]&lt;br /&gt;
&lt;br /&gt;
== Useful Tricks ==&lt;br /&gt;
&lt;br /&gt;
If you're using bash, it's worthwhile to set up tab completion of PIDs:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
$ complete -W &amp;quot;$(ola_rdm_get -l | xargs)&amp;quot; ola_rdm_get&lt;br /&gt;
$ complete -W &amp;quot;$(ola_rdm_get -l | xargs)&amp;quot; ola_rdm_set&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== RDM Sniffing with Saleae Logic ==&lt;br /&gt;
&lt;br /&gt;
OLA can now sniff RDM traffic with a [http://www.saleae.com/logic Saleae Logic].&lt;br /&gt;
&lt;br /&gt;
Check it out: [[Logic RDM Sniffer ]]!&lt;/div&gt;</summary>
		<author><name>Nightrune</name></author>	</entry>

	<entry>
		<id>https://wiki.openlighting.org/index.php?title=Logic_RDM_Sniffer&amp;diff=5565</id>
		<title>Logic RDM Sniffer</title>
		<link rel="alternate" type="text/html" href="https://wiki.openlighting.org/index.php?title=Logic_RDM_Sniffer&amp;diff=5565"/>
				<updated>2013-09-16T15:08:04Z</updated>
		
		<summary type="html">&lt;p&gt;Nightrune: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Image:Saleae-logic.jpg|thumb|200px|right|Saleae Logic]]&lt;br /&gt;
[[Image:Logic-sniffer.jpg|thumb|200px|right|The Logic as a 2 line DMX/RDM sniffer]]&lt;br /&gt;
&lt;br /&gt;
The [http://www.saleae.com/logic Saleae Logic] makes an excellent [[DMX]] / [[RDM]] sniffer.  With the Logic and a small amount of hardware you can build a sniffer for a fraction of the price of commercial units.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Parts ==&lt;br /&gt;
* A Logic or Logic 16, but see the note below.&lt;br /&gt;
* 485 driver circuit&lt;br /&gt;
* XLR connectors.&lt;br /&gt;
&lt;br /&gt;
== Electrical ==&lt;br /&gt;
&lt;br /&gt;
You need some hardware to convert from the differential 485 levels to a signal which the logic can understand.&lt;br /&gt;
&lt;br /&gt;
At the basic level you only need an RS-485 receiver like the Maxim MAX485 or Linear Technology LT1785 to translate from the DMX/RDM differential levels to a TTL level that the Saleae Logic understands.&lt;br /&gt;
[[File:RDMSnifferSchematic.jpg|thumb|center|400px|alt=Example Circuit]]&lt;br /&gt;
&lt;br /&gt;
Connecting this circuit to the Logic is fairly simple. Power the board with a MicroUSB Cable or from the +5V, and COM pins on the TTL connector. Then attach the Logic's grey Ground wire to the COM pin on the sniffer circuit, pull the DIR pin low to put the board in RX mode and connect your Logic's channel 1 (generally it's the black cable) to the RX pin. Finally Connect a DXM/RDM source to the board and make sure the green LED is flickering to show data is receiving on the TTL side.&lt;br /&gt;
&lt;br /&gt;
== Software ==&lt;br /&gt;
&lt;br /&gt;
=== Saleae Logic ===&lt;br /&gt;
&lt;br /&gt;
[[Image:Saleae-dmx.png|thumb|200px|right|The Logic App decoding DMX]]&lt;br /&gt;
&lt;br /&gt;
Saleae provides the [http://www.saleae.com/downloads Logic App] which works on Windows, Mac and Linux. The application has a plugin to decode DMX, but it doesn't understand RDM data. The tool is best for analyzing the signal timing rather than the high level messages.&lt;br /&gt;
&lt;br /&gt;
=== OLA Sniffer ===&lt;br /&gt;
&lt;br /&gt;
OLA has a text-based DMX/RDM sniffer that works with the Logic (it could easily be extended to work with the Logic 16). It can be found in [http://code.google.com/p/open-lighting/source/browse/#git%2Ftools%2Flogic tools/logic] directory of the OLA sources.&lt;br /&gt;
&lt;br /&gt;
Limitations:&lt;br /&gt;
* the sniffer doesn't understand DUB responses yet since it looks for breaks.&lt;br /&gt;
* it may struggle with signal timings that are at the edge of the E1.11 standard. If you experience problems with the sniffer please email the [http://groups.google.com/forum/#!forum/open-lighting Open Lighting Mailing List]&lt;/div&gt;</summary>
		<author><name>Nightrune</name></author>	</entry>

	<entry>
		<id>https://wiki.openlighting.org/index.php?title=Logic_RDM_Sniffer&amp;diff=5564</id>
		<title>Logic RDM Sniffer</title>
		<link rel="alternate" type="text/html" href="https://wiki.openlighting.org/index.php?title=Logic_RDM_Sniffer&amp;diff=5564"/>
				<updated>2013-09-16T14:58:56Z</updated>
		
		<summary type="html">&lt;p&gt;Nightrune: /* Electrical */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Image:Saleae-logic.jpg|thumb|200px|right|Saleae Logic]]&lt;br /&gt;
[[Image:Logic-sniffer.jpg|thumb|200px|right|The Logic as a 2 line DMX/RDM sniffer]]&lt;br /&gt;
&lt;br /&gt;
The [http://www.saleae.com/logic Saleae Logic] makes an excellent [[DMX]] / [[RDM]] sniffer.  With the Logic and a small amount of hardware you can build a sniffer for a fraction of the price of commercial units.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Parts ==&lt;br /&gt;
* A Logic or Logic 16, but see the note below.&lt;br /&gt;
* 485 driver circuit&lt;br /&gt;
* XLR connectors.&lt;br /&gt;
&lt;br /&gt;
== Electrical ==&lt;br /&gt;
&lt;br /&gt;
You need some hardware to convert from the differential 485 levels to a signal which the logic can understand.&lt;br /&gt;
&lt;br /&gt;
At the basic level you only need an RS-485 receiver like the Maxim MAX485 or Linear Technology LT1785 to translate from the DMX/RDM differential levels to a TTL level that the Saleae Logic understands.&lt;br /&gt;
[[File:RDMSnifferSchematic.jpg|thumb|center|400px|alt=Example Circuit]]&lt;br /&gt;
&lt;br /&gt;
== Software ==&lt;br /&gt;
&lt;br /&gt;
=== Saleae Logic ===&lt;br /&gt;
&lt;br /&gt;
[[Image:Saleae-dmx.png|thumb|200px|right|The Logic App decoding DMX]]&lt;br /&gt;
&lt;br /&gt;
Saleae provides the [http://www.saleae.com/downloads Logic App] which works on Windows, Mac and Linux. The application has a plugin to decode DMX, but it doesn't understand RDM data. The tool is best for analyzing the signal timing rather than the high level messages.&lt;br /&gt;
&lt;br /&gt;
=== OLA Sniffer ===&lt;br /&gt;
&lt;br /&gt;
OLA has a text-based DMX/RDM sniffer that works with the Logic (it could easily be extended to work with the Logic 16). It can be found in [http://code.google.com/p/open-lighting/source/browse/#git%2Ftools%2Flogic tools/logic] directory of the OLA sources.&lt;br /&gt;
&lt;br /&gt;
Limitations:&lt;br /&gt;
* the sniffer doesn't understand DUB responses yet since it looks for breaks.&lt;br /&gt;
* it may struggle with signal timings that are at the edge of the E1.11 standard. If you experience problems with the sniffer please email the [http://groups.google.com/forum/#!forum/open-lighting Open Lighting Mailing List]&lt;/div&gt;</summary>
		<author><name>Nightrune</name></author>	</entry>

	<entry>
		<id>https://wiki.openlighting.org/index.php?title=Logic_RDM_Sniffer&amp;diff=5563</id>
		<title>Logic RDM Sniffer</title>
		<link rel="alternate" type="text/html" href="https://wiki.openlighting.org/index.php?title=Logic_RDM_Sniffer&amp;diff=5563"/>
				<updated>2013-09-16T14:57:00Z</updated>
		
		<summary type="html">&lt;p&gt;Nightrune: /* Electrical */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Image:Saleae-logic.jpg|thumb|200px|right|Saleae Logic]]&lt;br /&gt;
[[Image:Logic-sniffer.jpg|thumb|200px|right|The Logic as a 2 line DMX/RDM sniffer]]&lt;br /&gt;
&lt;br /&gt;
The [http://www.saleae.com/logic Saleae Logic] makes an excellent [[DMX]] / [[RDM]] sniffer.  With the Logic and a small amount of hardware you can build a sniffer for a fraction of the price of commercial units.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Parts ==&lt;br /&gt;
* A Logic or Logic 16, but see the note below.&lt;br /&gt;
* 485 driver circuit&lt;br /&gt;
* XLR connectors.&lt;br /&gt;
&lt;br /&gt;
== Electrical ==&lt;br /&gt;
&lt;br /&gt;
You need some hardware to convert from the differential 485 levels to a signal which the logic can understand.&lt;br /&gt;
&lt;br /&gt;
At the basic level you only need an RS-485 receiver like the Maxim MAX485 or Linear Technology LT1785 to translate from the DMX/RDM differential levels to a TTL level that the Saleae Logic Understands.&lt;br /&gt;
[[File:RDMSnifferSchematic.jpg]]&lt;br /&gt;
&lt;br /&gt;
== Software ==&lt;br /&gt;
&lt;br /&gt;
=== Saleae Logic ===&lt;br /&gt;
&lt;br /&gt;
[[Image:Saleae-dmx.png|thumb|200px|right|The Logic App decoding DMX]]&lt;br /&gt;
&lt;br /&gt;
Saleae provides the [http://www.saleae.com/downloads Logic App] which works on Windows, Mac and Linux. The application has a plugin to decode DMX, but it doesn't understand RDM data. The tool is best for analyzing the signal timing rather than the high level messages.&lt;br /&gt;
&lt;br /&gt;
=== OLA Sniffer ===&lt;br /&gt;
&lt;br /&gt;
OLA has a text-based DMX/RDM sniffer that works with the Logic (it could easily be extended to work with the Logic 16). It can be found in [http://code.google.com/p/open-lighting/source/browse/#git%2Ftools%2Flogic tools/logic] directory of the OLA sources.&lt;br /&gt;
&lt;br /&gt;
Limitations:&lt;br /&gt;
* the sniffer doesn't understand DUB responses yet since it looks for breaks.&lt;br /&gt;
* it may struggle with signal timings that are at the edge of the E1.11 standard. If you experience problems with the sniffer please email the [http://groups.google.com/forum/#!forum/open-lighting Open Lighting Mailing List]&lt;/div&gt;</summary>
		<author><name>Nightrune</name></author>	</entry>

	<entry>
		<id>https://wiki.openlighting.org/index.php?title=File:RDMSnifferSchematic.jpg&amp;diff=5562</id>
		<title>File:RDMSnifferSchematic.jpg</title>
		<link rel="alternate" type="text/html" href="https://wiki.openlighting.org/index.php?title=File:RDMSnifferSchematic.jpg&amp;diff=5562"/>
				<updated>2013-09-16T14:56:18Z</updated>
		
		<summary type="html">&lt;p&gt;Nightrune: Example of an RDM Sniffer Schematic.&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Example of an RDM Sniffer Schematic.&lt;/div&gt;</summary>
		<author><name>Nightrune</name></author>	</entry>

	<entry>
		<id>https://wiki.openlighting.org/index.php?title=Logic_RDM_Sniffer&amp;diff=5561</id>
		<title>Logic RDM Sniffer</title>
		<link rel="alternate" type="text/html" href="https://wiki.openlighting.org/index.php?title=Logic_RDM_Sniffer&amp;diff=5561"/>
				<updated>2013-09-16T14:52:15Z</updated>
		
		<summary type="html">&lt;p&gt;Nightrune: /* Electrical */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Image:Saleae-logic.jpg|thumb|200px|right|Saleae Logic]]&lt;br /&gt;
[[Image:Logic-sniffer.jpg|thumb|200px|right|The Logic as a 2 line DMX/RDM sniffer]]&lt;br /&gt;
&lt;br /&gt;
The [http://www.saleae.com/logic Saleae Logic] makes an excellent [[DMX]] / [[RDM]] sniffer.  With the Logic and a small amount of hardware you can build a sniffer for a fraction of the price of commercial units.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Parts ==&lt;br /&gt;
* A Logic or Logic 16, but see the note below.&lt;br /&gt;
* 485 driver circuit&lt;br /&gt;
* XLR connectors.&lt;br /&gt;
&lt;br /&gt;
== Electrical ==&lt;br /&gt;
&lt;br /&gt;
You need some hardware to convert from the differential 485 levels to a signal which the logic can understand.&lt;br /&gt;
&lt;br /&gt;
At the basic level you only need an RS-485 receiver like the Maxim MAX485 or Linear Technology LT1785 to translate from the DMX/RDM differential levels to a TTL level that the Saleae Logic Understands.&lt;br /&gt;
[[File:Example.jpg]]&lt;br /&gt;
&lt;br /&gt;
== Software ==&lt;br /&gt;
&lt;br /&gt;
=== Saleae Logic ===&lt;br /&gt;
&lt;br /&gt;
[[Image:Saleae-dmx.png|thumb|200px|right|The Logic App decoding DMX]]&lt;br /&gt;
&lt;br /&gt;
Saleae provides the [http://www.saleae.com/downloads Logic App] which works on Windows, Mac and Linux. The application has a plugin to decode DMX, but it doesn't understand RDM data. The tool is best for analyzing the signal timing rather than the high level messages.&lt;br /&gt;
&lt;br /&gt;
=== OLA Sniffer ===&lt;br /&gt;
&lt;br /&gt;
OLA has a text-based DMX/RDM sniffer that works with the Logic (it could easily be extended to work with the Logic 16). It can be found in [http://code.google.com/p/open-lighting/source/browse/#git%2Ftools%2Flogic tools/logic] directory of the OLA sources.&lt;br /&gt;
&lt;br /&gt;
Limitations:&lt;br /&gt;
* the sniffer doesn't understand DUB responses yet since it looks for breaks.&lt;br /&gt;
* it may struggle with signal timings that are at the edge of the E1.11 standard. If you experience problems with the sniffer please email the [http://groups.google.com/forum/#!forum/open-lighting Open Lighting Mailing List]&lt;/div&gt;</summary>
		<author><name>Nightrune</name></author>	</entry>

	<entry>
		<id>https://wiki.openlighting.org/index.php?title=Open_Lighting_Project&amp;diff=5521</id>
		<title>Open Lighting Project</title>
		<link rel="alternate" type="text/html" href="https://wiki.openlighting.org/index.php?title=Open_Lighting_Project&amp;diff=5521"/>
				<updated>2013-07-31T11:44:37Z</updated>
		
		<summary type="html">&lt;p&gt;Nightrune: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;The Open Lighting Project is a multi-faceted effort aimed at accelerating the adoption of new, standardized control protocols, while also providing high quality, reliable, open software for the lighting industry. This site acts as a resource for anyone looking for information about DMX software and the associated control systems, as well as a variety of Open Source and free lighting software.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;table style=&amp;quot;width: 100%; margin:4px 0 0 0; background:none; border-spacing: 5px;&amp;quot;&amp;gt;&lt;br /&gt;
 &amp;lt;tr&amp;gt;&lt;br /&gt;
  &amp;lt;td style=&amp;quot;width:45%; border:1px solid #cedff2; background:#f5faff; vertical-align:top; padding: 4px&amp;quot;&amp;gt;&lt;br /&gt;
    [[Image:OLA-Logo-Fitted-48px.png|right|link=OLA]]&lt;br /&gt;
    &amp;lt;h2 style=&amp;quot;float:left; font-size:120%; padding: .2em; margin:3px; font-weight:bold;&amp;quot;&amp;gt;[[OLA | The Open Lighting Architecture]]&amp;lt;/h2&amp;gt;&lt;br /&gt;
    &amp;lt;div style=&amp;quot;clear: left&amp;quot;&amp;gt;&lt;br /&gt;
The [[OLA | Open Lighting Architecture]] provides a framework for distributing lighting control information. It supports many protocols such as E1.31 (sACN), ArtNet, ShowNet, Pathport, RDM and over a dozen USB devices. It can run as a standalone service, which is useful for converting signals between protocols, or alternatively it can be used as the backend for [[:Category:Controllers | Controller Applications]]. OLA runs on a many different platforms including ARM, which makes it a perfect fit for low cost Ethernet to DMX gateways.&lt;br /&gt;
    &amp;lt;/div&amp;gt;&lt;br /&gt;
  &amp;lt;/td&amp;gt;&lt;br /&gt;
  &amp;lt;td style=&amp;quot;width:45%; border:1px solid #cedff2; background:#f5faff; vertical-align:top; padding: 4px&amp;quot;&amp;gt;&lt;br /&gt;
    [[Image:rdm-logo-small.png|right|link=]]&lt;br /&gt;
    &amp;lt;h2 style=&amp;quot;float:left; font-size:120%; padding: .2em; margin:3px; font-weight:bold;&amp;quot;&amp;gt;[[RDM_Responder_Testing | RDM Responder Tests]]&amp;lt;/h2&amp;gt;&lt;br /&gt;
    &amp;lt;div style=&amp;quot;clear: left&amp;quot;&amp;gt;&lt;br /&gt;
Testing RDM Responder used to involve manually sending commands and verifying the responses. Not any longer! The [[RDM_Responder_Testing | RDM Responder Tests]] automate all of this and provide a detailed breakdown of how well a responder complies with the [[E1.20]] (RDM) standard. This saves time during the product development process and raises the quality of RDM implementations across the industry.&lt;br /&gt;
&lt;br /&gt;
For questions about the RDM Responder tests, email the  [http://groups.google.com/group/rdm-testing RDM Testing List].&lt;br /&gt;
    &amp;lt;/div&amp;gt;&lt;br /&gt;
  &amp;lt;/td&amp;gt;&lt;br /&gt;
 &amp;lt;/tr&amp;gt;&lt;br /&gt;
 &amp;lt;tr&amp;gt;&amp;lt;td colspan=&amp;quot;2&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
 &amp;lt;tr&amp;gt;&lt;br /&gt;
  &amp;lt;td style=&amp;quot;width:45%; border:1px solid #cedff2; background:#f5faff; vertical-align:top; padding: 4px&amp;quot;&amp;gt;&lt;br /&gt;
    [[Image:raspi-logo-small.png|right|link=]]&lt;br /&gt;
    &amp;lt;h2 style=&amp;quot;float:left; font-size:120%; padding: .2em; margin:3px; font-weight:bold;&amp;quot;&amp;gt;[[OLA_Raspberry_Pi | OLA on the Raspberry Pi]]&amp;lt;/h2&amp;gt;&lt;br /&gt;
    &amp;lt;div style=&amp;quot;clear: left&amp;quot;&amp;gt;&lt;br /&gt;
The [http://www.raspberrypi.org/ Raspberry Pi] is one of the most popular platforms for running [[OLA]]. With the addition of a USB to DMX device, one can build a low cost, but fully functional Ethernet gateway. The [[OLA_Raspberry_Pi | OLA on Raspberry Pi]] tutorial has a step by step guide to installing OLA on the Pi.&lt;br /&gt;
    &amp;lt;/div&amp;gt;&lt;br /&gt;
  &amp;lt;/td&amp;gt;&lt;br /&gt;
&lt;br /&gt;
  &amp;lt;td style=&amp;quot;width:45%; border:1px solid #cedff2; background:#f5faff; vertical-align:top; padding: 4px&amp;quot;&amp;gt;&lt;br /&gt;
    [[Image:Robin-1200.png|right|link=]]&lt;br /&gt;
    &amp;lt;h2 style=&amp;quot;float:left; font-size:120%; padding: .2em; margin:3px; font-weight:bold;&amp;quot;&amp;gt;rdm.openlighting.org&amp;lt;/h2&amp;gt;&lt;br /&gt;
    &amp;lt;div style=&amp;quot;clear: left&amp;quot;&amp;gt;&lt;br /&gt;
The http://rdm.openlighting.org site contains an index of RDM-enabled products as well as the specifications for many of the manufacturer specific PIDs. The site has recently been expanded to display the results of the RDM Responder Tests. The data on the site is available free of charge through APIs. &lt;br /&gt;
    &amp;lt;/div&amp;gt;&lt;br /&gt;
  &amp;lt;/td&amp;gt;&lt;br /&gt;
 &amp;lt;/tr&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td colspan=&amp;quot;2&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
 &amp;lt;tr&amp;gt;&lt;br /&gt;
  &amp;lt;td style=&amp;quot;width:45%; border:1px solid #cedff2; background:#f5faff; vertical-align:top; padding: 4px&amp;quot;&amp;gt;&lt;br /&gt;
    [[Image:Email-icon.png|right|link=]]&lt;br /&gt;
    &amp;lt;h2 style=&amp;quot;float:left; font-size:120%; padding: .2em; margin:3px; font-weight:bold;&amp;quot;&amp;gt;Contact / Support&amp;lt;/h2&amp;gt;&lt;br /&gt;
    &amp;lt;div style=&amp;quot;clear: left&amp;quot;&amp;gt;&lt;br /&gt;
Since this is an Open Source project, there is no commercial support for our products at this time. There are a number of ways of reaching the community though:&lt;br /&gt;
&lt;br /&gt;
* Primary User &amp;amp; Developer Discussion [http://groups.google.com/group/open-lighting Open Lighting Discuss] (typically a few messages per day).&lt;br /&gt;
* Announcements are posted to [http://groups.google.com/group/open-lighting-announce Open Lighting Announce] (low volume, typically 1-2 per month)&lt;br /&gt;
* RDM Testing Discussion [http://groups.google.com/group/rdm-testing RDM Testing].&lt;br /&gt;
* IRC #openlighting on freenode.net (or [http://webchat.freenode.net/?channels=openlighting webchat])&lt;br /&gt;
There is also an [https://plus.google.com/106460627923808853381 Open Lighting Community] on Google+. This is less OLA centric and more about sharing cool lighting projects people are working on.&lt;br /&gt;
    &amp;lt;/div&amp;gt;&lt;br /&gt;
  &amp;lt;/td&amp;gt;&lt;br /&gt;
&lt;br /&gt;
  &amp;lt;td style=&amp;quot;width:45%; border:1px solid #cedff2; background:#f5faff; vertical-align:top; padding: 4px&amp;quot;&amp;gt;&lt;br /&gt;
    &amp;lt;h2 style=&amp;quot;float:left; font-size:120%; padding: .2em; margin:3px; font-weight:bold;&amp;quot;&amp;gt;Other Projects&amp;lt;/h2&amp;gt;&lt;br /&gt;
    &amp;lt;div style=&amp;quot;clear: left&amp;quot;&amp;gt;&lt;br /&gt;
* [[libartnet]]. The library that started it all, libartnet is an [[ArtNet]] implementation for Mac, Linux, Windows &amp;amp; iPhone.&lt;br /&gt;
* [[Logic RDM Sniffer]] - Use a [http://saleae.com/logic Saleae Logic] device as a RDM analyzer. &lt;br /&gt;
* [[Arduino RGB Mixer]], open source firmware for Arduinos, so that they can be used as a simple RGB Color Mixer. Now with RDM support!&lt;br /&gt;
* [[OLA_DMX_Trigger | DMX Trigger]], this can execute command line programs based on DMX values. It's useful for building DMX controlled media players.&lt;br /&gt;
* [[E1.33 SLP SA Tests]], similar to the RDM Responder Tests, this performs tests against a RDMNet Device's SLP implementation.&lt;br /&gt;
* [[OLA LED Pixels]], drive pixel strings using OLA&lt;br /&gt;
    &amp;lt;/div&amp;gt;&lt;br /&gt;
  &amp;lt;/td&amp;gt;&lt;br /&gt;
 &amp;lt;/tr&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td colspan=&amp;quot;2&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
 &amp;lt;tr&amp;gt;&lt;br /&gt;
  &amp;lt;td style=&amp;quot;width:45%; border:1px solid #cedff2; background:#f5faff; vertical-align:top; padding: 4px&amp;quot;&amp;gt;&lt;br /&gt;
    &amp;lt;h2 style=&amp;quot;float:left; font-size:120%; padding: .2em; margin:3px; font-weight:bold;&amp;quot;&amp;gt;Project Supporters&amp;lt;/h2&amp;gt;&lt;br /&gt;
    &amp;lt;div style=&amp;quot;clear: left&amp;quot;&amp;gt;&lt;br /&gt;
Many individuals &amp;amp; organizations have supported the project over the years. We're grateful to all of them.&lt;br /&gt;
&lt;br /&gt;
* [http://www.anyma.ch Anyma], provided a [[Anyma_uDMX|uDMX]]&lt;br /&gt;
* [[Artistic Licence]], provided a [[Net-Lynx]] &amp;amp; Down-Lynx for Art-Net / RDM testing and a [[Rail-Tran]] to test [[RDM]] support&lt;br /&gt;
* Andrew Frazer, who sponsored the development of ola_trigger with a [[RDM USB Pro]] &lt;br /&gt;
* [http://www.creativelighting.com.au/ Creative Lighting], provided a [[SLAMMO XC-1]] &amp;amp; [[ADDICT]] for [[RDM]] testing.&lt;br /&gt;
* [[Enttec]], provided a [[DMX USB Pro]]&lt;br /&gt;
* Eric Johnson, for hosting the server used to test &amp;amp; debug much of the RDM code.&lt;br /&gt;
* Florian from eventa.ag who donated a [[StageProfi]] and a [[USBDMX2]]&lt;br /&gt;
* [http://www.goddarddesign.com/ Goddard Design], who made available a  [[MiniDMXter]]&lt;br /&gt;
* Jason Kyle from [http://www.DMXking.com DMXKing.com] provided a [[DMXking USB DMX512-A]]&lt;br /&gt;
* [[JESE]], provided a [[DMX-TRI]] &amp;amp;  [[RDM-TRI]] &amp;amp; Tempest Enclosure to test the RDM implementation. &lt;br /&gt;
* [http://www.ljusdesign.se LjusDesign AB] who donated 7 RDM splitters.&lt;br /&gt;
* [http://www.lumenradio.com/ LumenRadio] who provided a Nova TX2 RDM, Nova RX RDM and Nova FX units and a Raspberry Pi.&lt;br /&gt;
* [http://www.martin.com Martin Professional A/S] which loaned a Mac 700 for RDM testing &lt;br /&gt;
* [http://www.milinst.co.uk/ Milford Instruments] who sent 3 RDMChips for testing.&lt;br /&gt;
* Peter Kirkup, from [http://www.zero88.com/ Zero 88] who donated a Betapack 3&lt;br /&gt;
* Petr from [[ROBE Lighting]] who loaned a [[Robe Universal Interface]] and [http://www.robe.cz/products/article/robin-600e-spot/ Robin 600]&lt;br /&gt;
* [http://www.sandsys.com/ Sandsys], donated a [http://www.sandsys.com/products/SB-AAA2100.htm SandBox]&lt;br /&gt;
* Shaun Jackman, answered questions about the [[:Category:Pathport|Pathport]] Protocol&lt;br /&gt;
* [http://soundlight.de/ SoundLight] who loaned a 3604PWM-H device&lt;br /&gt;
* [http://www.waapa.ecu.edu.au West Australian Academy of Performing Arts] (WAAPA) for access to a [[Strand Lighting]] console.&lt;br /&gt;
&lt;br /&gt;
    &amp;lt;/div&amp;gt;&lt;br /&gt;
  &amp;lt;/td&amp;gt;&lt;br /&gt;
&lt;br /&gt;
  &amp;lt;td style=&amp;quot;width:45%; border:1px solid #cedff2; background:#f5faff; vertical-align:top; padding: 4px&amp;quot;&amp;gt;&lt;br /&gt;
    &amp;lt;h2 style=&amp;quot;float:left; font-size:120%; padding: .2em; margin:3px; font-weight:bold;&amp;quot;&amp;gt;Get Involved&amp;lt;/h2&amp;gt;&lt;br /&gt;
    &amp;lt;div style=&amp;quot;clear: left&amp;quot;&amp;gt;&lt;br /&gt;
There is plenty of opportunity to get involved. If you would like to help with any of the following (or have your own ideas) then please get in touch with us on the [http://groups.google.com/group/open-lighting Open Lighting Group]&lt;br /&gt;
&lt;br /&gt;
* Technical Writers, the documentation could do with some cleanup.&lt;br /&gt;
* Packagers, we need people to build binary packages for Mac, Debian/Ubuntu and RPM-based distros&lt;br /&gt;
* Windows programmers, are you interested in helping [[Building_OLA_for_Windows| port OLA to Windows]]?  &lt;br /&gt;
* Java programmers, we need someone to write the Java client API [http://code.google.com/p/linux-lighting/issues/detail?id=15 ]&lt;br /&gt;
* Equipment donation, do you own or know of a [[:Category:USB | USB interface]] or RDM device we don't support yet? Consider lending it to us.&lt;br /&gt;
* Web designers, the web UI could do with a facelift.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The programming team behind OLA consists of:&lt;br /&gt;
* Bastien Andrès, contributed to the dmx4linux plugin&lt;br /&gt;
* Harry F, for the Eurolite USB Pro code&lt;br /&gt;
* Heikki Junnila, bug fixes for the debian packaging files&lt;br /&gt;
* Laurent  (Renzo), Debian packages, FreeBSD &amp;amp; RDM testing.&lt;br /&gt;
* Masaki Muranaka, various patches&lt;br /&gt;
* Peter Newman, man pages, various patches&lt;br /&gt;
* Nicolas, for the win32 port of libartnet&lt;br /&gt;
* Ravindra Nath Kakarla, RDM Test Server (Part of [http://www.google-melange.com/gsoc/profile/organization/google/gsoc2012/openlighting Google Summer of Code 2012] ).&lt;br /&gt;
* Rowan Maclachlan (hippy) for various changes&lt;br /&gt;
* Joshua Moyerman, various changes.&lt;br /&gt;
* Carsten Presser , Karate Light plugin&lt;br /&gt;
* Rui Barreiros for the FTDI plugin&lt;br /&gt;
* Sean Sill, RDM, doxygen comments.&lt;br /&gt;
* Tobi Schäfer, for the MacPort files&lt;br /&gt;
    &amp;lt;/div&amp;gt;&lt;br /&gt;
  &amp;lt;/td&amp;gt;&lt;br /&gt;
 &amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;/table&amp;gt;&lt;br /&gt;
&lt;br /&gt;
__NOTOC__&lt;/div&gt;</summary>
		<author><name>Nightrune</name></author>	</entry>

	<entry>
		<id>https://wiki.openlighting.org/index.php?title=DMX_USB_Pro&amp;diff=5513</id>
		<title>DMX USB Pro</title>
		<link rel="alternate" type="text/html" href="https://wiki.openlighting.org/index.php?title=DMX_USB_Pro&amp;diff=5513"/>
				<updated>2013-07-26T18:02:27Z</updated>
		
		<summary type="html">&lt;p&gt;Nightrune: Updated deprecated link to LLA&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:USB]]&lt;br /&gt;
&lt;br /&gt;
[[Image:Dmxusb_pro.jpg|right]]&lt;br /&gt;
&lt;br /&gt;
Link: http://www.enttec.com/index.php?main_menu=Products&amp;amp;prod=70304&amp;amp;show=description&amp;amp;name=dmxusbpro&amp;lt;br&amp;gt;&lt;br /&gt;
Made by: [[Enttec]] &amp;lt;br&amp;gt;&lt;br /&gt;
{{Features|win=yes|osx=yes|linux=yes|tx=yes|rx=yes|rdm=yes}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The pro widget unlike it's little brother (The Open DMX USB) contains a microprocessor (ATMEGA88) responsible for framing and transmission, or reception of dmx. Also it's USB interface is a FTDI FT245BM, so VCP (virtual com port) drivers make programming easy as opening a serial port and sending/receiving!&lt;br /&gt;
&lt;br /&gt;
It has 1500v dmx line isolation, A green LED which indicates RX or TX activity, and gold plated Neutrik XLR's (1xmale, 1xfemale wired in parallel). Later versions have NewTide clones of the genuine Neutrik XLR's.&lt;br /&gt;
&lt;br /&gt;
The timings of the transmitted DMX signal can be adjusted.&lt;br /&gt;
According the [[Enttec]] [http://enttec.com web site], it has [[RDM]] support in V2 firmware, the unit ships with V1 by default, see [http://www.enttec.com/index.php?main_menu=Products&amp;amp;prod=70304&amp;amp;show=firmware] for details.&lt;br /&gt;
&lt;br /&gt;
Enttec provides programs to update the firmware on Windows and Mac. [[OLA]] has a tool to update the firmware which works on Linux and Mac, otherwise [http://kev.coolcavemen.com/2009/05/enttec-dmx-usb-firmware-upgrade-with-qemu/ qemu] can be used.&lt;br /&gt;
&lt;br /&gt;
Earlier units did not have serial numbers programmed and this may affect the ability of certain applications to identify multiple Pro units connected simultaneously.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;b&amp;gt;Related Products:&amp;lt;/b&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* [[RDM USB Pro]]&lt;br /&gt;
* [[Open DMX USB]]&lt;br /&gt;
* [[DMXking USB DMX512-A]]&lt;br /&gt;
* [[Pro Toolkit]]&lt;br /&gt;
* [[StageConsole]]&lt;br /&gt;
* [[MiniStageConsole]]&lt;/div&gt;</summary>
		<author><name>Nightrune</name></author>	</entry>

	<entry>
		<id>https://wiki.openlighting.org/index.php?title=Open_Lighting_Architecture&amp;diff=5498</id>
		<title>Open Lighting Architecture</title>
		<link rel="alternate" type="text/html" href="https://wiki.openlighting.org/index.php?title=Open_Lighting_Architecture&amp;diff=5498"/>
				<updated>2013-07-17T16:29:12Z</updated>
		
		<summary type="html">&lt;p&gt;Nightrune: Added a link to the generated Doxygen Docs&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Image:OLA-Logo-Fitted-48px.png|right]]&lt;br /&gt;
Link: http://code.google.com/p/open-lighting/ &amp;lt;br&amp;gt;&lt;br /&gt;
{{Features|free=yes|tx=yes|rx=yes|linux=yes|osx=yes|http=yes|rdm=yes}}&lt;br /&gt;
[[Image:Ola-download.png |right|link=http://opendmx.net/index.php/Download_%26_Install_OLA]]&lt;br /&gt;
[[Image:Llad_home.png| thumb |200px|right|Universe Settings]]&lt;br /&gt;
[[Image:Ola-rdm.png|thumb|200px|right|RDM Devices Page]]&lt;br /&gt;
[[Image:OLA_patching.png|thumb|200px|right|Drag &amp;amp; Drop RDM Patching]]&lt;br /&gt;
[[Image:Ola-mobile.png|thumb|200px|right|Mobile UI]]&lt;br /&gt;
&lt;br /&gt;
__NOTOC__&lt;br /&gt;
The Open Lighting Architecture (OLA) is part of the [[Open Lighting Project]] and provides applications with a mechanism to send and receive [[DMX512]] &amp;amp; [[RDM]] commands using hardware devices and DMX over IP protocols. This enables [[:Category:Controllers | software lighting controllers]] to communicate with hardware either via Ethernet or traditional DMX512 networks.&lt;br /&gt;
&lt;br /&gt;
OLA can also convert DMX512 data sent using DMX over IP protocols from one format to another, allowing devices from different manufacturers to interact with one another. For example a [[Strand_Lighting|Strand]] Lighting Console using ShowNet can send DMX512 to an [[Enttec]] [[DmxEtherGate MKII|EtherGate]]. When combined with a physical DMX interface such as the [[DMX USB Pro]], OLA can send and receive data from wired DMX512 networks.&lt;br /&gt;
&lt;br /&gt;
==Supported Protocols==&lt;br /&gt;
&lt;br /&gt;
{| border=1 cellspacing=&amp;quot;0&amp;quot;&lt;br /&gt;
! '''Protocol'''!! Linux !! '''Mac OS X'''  || '''FreeBSD'''&lt;br /&gt;
|-&lt;br /&gt;
|| [[:Category:ArtNet|ArtNet, ArtNet 2, ArtNet 3]]   || [[Image:Green-tick.png|center]] [[Image:Rdm.gif|center]] || [[Image:Green-tick.png|center]][[Image:Rdm.gif|center]] || [[Image:Green-tick.png|center]][[Image:Rdm.gif|center]]&lt;br /&gt;
|-&lt;br /&gt;
|| [[E1.31]] / [[ACN]] || [[Image:Green-tick.png|center]]  || [[Image:Green-tick.png|center]]  || [[Image:Green-tick.png|center]]&lt;br /&gt;
|-&lt;br /&gt;
|| [[:Category:ESP Net|ESP Net]] || [[Image:Green-tick.png|center]]  || [[Image:Green-tick.png|center]]  || [[Image:Green-tick.png|center]]&lt;br /&gt;
|-&lt;br /&gt;
|| [[KiNET]] ||  [[Image:Trans.gif|center]]  ||  [[Image:Trans.gif|center]] ||  [[Image:Trans.gif|center]] &lt;br /&gt;
|-&lt;br /&gt;
|| [[OSC]] (Open Sound Control)  || [[Image:Green-tick.png|center]]  || [[Image:Green-tick.png|center]] || ?&lt;br /&gt;
|-&lt;br /&gt;
|| [[:Category:Pathport|Pathport]]  || [[Image:Green-tick.png|center]]  || [[Image:Green-tick.png|center]] || [[Image:Green-tick.png|center]]&lt;br /&gt;
|-&lt;br /&gt;
|| [[:Category:Sandnet|Sandnet]] || [[Image:Green-tick.png|center]]  || [[Image:Green-tick.png|center]] || [[Image:Green-tick.png|center]]&lt;br /&gt;
|-&lt;br /&gt;
|| [[:Category:ShowNet|ShowNet]] || [[Image:Green-tick.png|center]]  || [[Image:Green-tick.png|center]] || [[Image:Green-tick.png|center]]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Supported Devices==&lt;br /&gt;
&lt;br /&gt;
{| border=1 cellspacing=&amp;quot;0&amp;quot;&lt;br /&gt;
! '''Device'''!! Linux !! '''Mac OS X'''  || '''FreeBSD'''&lt;br /&gt;
|-&lt;br /&gt;
||  [[Anyma uDMX]] || [[Image:Trans.gif|center]] || [[Image:Trans.gif|center]]  || ?&lt;br /&gt;
|-&lt;br /&gt;
|| [[Arduino RGB Mixer]] || [[Image:Green-tick.png|center]] [[Image:Rdm.gif|center]]  || [[Image:Green-tick.png|center]] [[Image:Rdm.gif|center]] || ?&lt;br /&gt;
|-&lt;br /&gt;
|| [[DMX 4 Linux]] || [[Image:Trans.gif|center]]  ||  ||  ?&lt;br /&gt;
|-&lt;br /&gt;
|| [[DMX USB Pro]] || [[Image:Trans.gif|center]] [[Image:Recv.gif|center]] [[Image:Rdm.gif|center]]  || [[Image:Trans.gif|center]] [[Image:Recv.gif|center]] [[Image:Rdm.gif|center]]  ||  [[Image:Trans.gif|center]] [[Image:Recv.gif|center]] [[Image:Rdm.gif|center]]&lt;br /&gt;
|-&lt;br /&gt;
|| [[DMX USB Pro MkII]] || [[Image:Trans.gif|center]] [[Image:Recv.gif|center]] [[Image:Rdm.gif|center]]  || [[Image:Trans.gif|center]] [[Image:Recv.gif|center]] [[Image:Rdm.gif|center]]  ||  [[Image:Trans.gif|center]] [[Image:Recv.gif|center]] [[Image:Rdm.gif|center]]&lt;br /&gt;
|-&lt;br /&gt;
|| [[DMX-TRI]] || [[Image:Trans.gif|center]] || [[Image:Trans.gif|center]]  || [[Image:Trans.gif|center]]&lt;br /&gt;
|-&lt;br /&gt;
|| [[DMXking USB DMX512-A]] || [[Image:Trans.gif|center]] [[Image:Recv.gif|center]] || [[Image:Trans.gif|center]] [[Image:Recv.gif|center]] || ?&lt;br /&gt;
|-&lt;br /&gt;
|| [[DMXter4 RDM]] / [[MiniDMXter]] || [[Image:Rdm.gif|center]] || [[Image:Rdm.gif|center]] || ?&lt;br /&gt;
|-&lt;br /&gt;
|| [[Eurolite USB DMX512 PRO]] || [[Image:Trans.gif|center]] || [[Image:Trans.gif|center]]  || ?&lt;br /&gt;
|-&lt;br /&gt;
|| [[KarateLight]] || [[Image:Trans.gif|center]] ||  || ?&lt;br /&gt;
|-&lt;br /&gt;
|| [[Open DMX USB]] || [[Image:Trans.gif|center]]  ||  || ?&lt;br /&gt;
|-&lt;br /&gt;
|| [[Packetheads USB_DMX Dongle]] ||  [[Image:Green-tick.png|center]]  ||  [[Image:Green-tick.png|center]]  || ?&lt;br /&gt;
|-&lt;br /&gt;
|| [[RDM USB Pro]] || [[Image:Trans.gif|center]]  [[Image:Recv.gif|center]]  || [[Image:Trans.gif|center]]  [[Image:Recv.gif|center]] || ?&lt;br /&gt;
|-&lt;br /&gt;
|| [[RDM-TRI]] || [[Image:Trans.gif|center]] [[Image:Rdm.gif|center]] || [[Image:Trans.gif|center]] [[Image:Rdm.gif|center]] ||   [[Image:Trans.gif|center]] [[Image:Rdm.gif|center]] &lt;br /&gt;
|-&lt;br /&gt;
|| [[Robe Universal Interface]] || [[Image:Trans.gif|center]]  [[Image:Recv.gif|center]] [[Image:Rdm.gif|center]] || [[Image:Trans.gif|center]]  [[Image:Recv.gif|center]] [[Image:Rdm.gif|center]] || ?&lt;br /&gt;
|-&lt;br /&gt;
|| [[RUNIT WTX]] || [[Image:Trans.gif|center]]  [[Image:Recv.gif|center]] [[Image:Rdm.gif|center]] || [[Image:Trans.gif|center]]  [[Image:Recv.gif|center]] [[Image:Rdm.gif|center]] ||  ?&lt;br /&gt;
|-&lt;br /&gt;
|| SPI || [[Image:Trans.gif|center]]  ||   || ?&lt;br /&gt;
|-&lt;br /&gt;
|| [[StageProfi]] || [[Image:Trans.gif|center]]  || [[Image:Trans.gif|center]] (Ethernet version only) || ?&lt;br /&gt;
|-&lt;br /&gt;
|| [http://machosehead.wordpress.com/2010/06/12/udmx_asp/ uDMX_asp] || [[Image:Trans.gif|center]]  || [[Image:Trans.gif|center]]  || ?&lt;br /&gt;
|-&lt;br /&gt;
|| [[ultraDMX Pro]] ||  [[Image:Trans.gif|center]] [[Image:Recv.gif|center]]  || [[Image:Trans.gif|center]] [[Image:Recv.gif|center]]  || ?&lt;br /&gt;
|-&lt;br /&gt;
|| [[ultraDMX Micro]] ||  [[Image:Trans.gif|center]] [[Image:Recv.gif|center]]  || [[Image:Trans.gif|center]] [[Image:Recv.gif|center]]  || ?&lt;br /&gt;
|-&lt;br /&gt;
|| [[USBDMX2]] || [[Image:Trans.gif|center]]  || [[Image:Trans.gif|center]]  || ?&lt;br /&gt;
|-&lt;br /&gt;
|| [http://www.soh.cz/produkty/modul-usb-dmx512 USB-DMX512] || [[Image:Trans.gif|center]]  || [[Image:Trans.gif|center]]  || ?&lt;br /&gt;
|-&lt;br /&gt;
|| [[Velleman K8062]] || [[Image:Trans.gif|center]]  || [[Image:Trans.gif|center]]  || ?&lt;br /&gt;
|-&lt;br /&gt;
|| [[Velleman_K8062_Upgrade|VX8062]] || [[Image:Trans.gif|center]]  || [[Image:Trans.gif|center]]  || ?&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Getting Started==&lt;br /&gt;
&lt;br /&gt;
Start here if you've never used OLA before and read these in order.&lt;br /&gt;
* [[Download &amp;amp; Install OLA]]&lt;br /&gt;
* [[Using OLA]] - A basic introduction&lt;br /&gt;
* [[OLA Command Line Tools]] - Documentation for the tools in ola-examples&lt;br /&gt;
* [[OLA Device Specific Configuration]]&lt;br /&gt;
* [[OLA Tips &amp;amp; Tricks]]&lt;br /&gt;
* [[RDM with OLA]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;b&amp;gt;Tutorials&amp;lt;/b&amp;gt;&lt;br /&gt;
* [[OLA on Windows with VMWare]]&lt;br /&gt;
* [[OLA Live CD]], instructions on how to use the Live CD&lt;br /&gt;
* [[OLA Raspberry Pi]]&lt;br /&gt;
* [[OLA on Beaglebone]]&lt;br /&gt;
* [[OlaOutput Max External]] - Setup OlaOutput on Mac OS X to send DMX messages from Max/MSP/Jitter&lt;br /&gt;
* [[OLAGuruPlug]] - Running OLA on a [http://www.globalscaletechnologies.com/c-4-guruplugs.aspx GuruPlug]&lt;br /&gt;
* [[OlaLED]] - control RGB LED via http&lt;br /&gt;
* [[OLA RDM Responder Testing]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;b&amp;gt;Advanced Topics:&amp;lt;/b&amp;gt;&lt;br /&gt;
* [[OLA Merging Algorithms]]&lt;br /&gt;
* [[OLA DiffServ support]] (QOS settings)&lt;br /&gt;
* [[OLA DMX Trigger]]&lt;br /&gt;
* [[OLA Patch persistency]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;b&amp;gt;Developer Documentation:&amp;lt;/b&amp;gt;&lt;br /&gt;
* [[OLA developer info]] - about the source code and structure&lt;br /&gt;
* [http://docs.openlighting.org/doc OLA Doxygen Docs] - Generated Doxygen docs aimed at developers creating clients.&lt;br /&gt;
* OLA APIs&lt;br /&gt;
** Protobufs Based&lt;br /&gt;
*** [[OLA Client API]] - the C++ API&lt;br /&gt;
*** [[OLA Python API]] - easy DMX programming&lt;br /&gt;
*** [http://code.google.com/p/open-lighting/source/browse/#git%2Fjava Java] - currently a work in progress&lt;br /&gt;
** Alternatives&lt;br /&gt;
*** JSON - Browse to /help on your OLA webserver to see the available commands (append ?help=1 to the end of a command for more info in newer versions of OLA)&lt;br /&gt;
*** [[OSC]] - Not technically an API, but not strictly a lightly protocol either, enable the OSC plugin and use it to communicate with OLA from a variety of software&lt;br /&gt;
* [[Build OLA Mac Packages]] - notes for building the .dmg images&lt;br /&gt;
* [[Building OLA for Windows]] - Notes on Windows support (in progress)&lt;br /&gt;
* [[Cross Compiling OLA]]&lt;br /&gt;
* [[OLA Buildbot]] - For continuous build and testing&lt;br /&gt;
* [[Using OLA with Xcode]] - on a Mac, in Objective-C++&lt;br /&gt;
* [[Writing RDM Responder Tests]]&lt;br /&gt;
* [[Port Throttling]] &lt;br /&gt;
* [[RDM PID Definitions]]&lt;br /&gt;
* [[OLA Performance Stats]]&lt;br /&gt;
* [[OLA TimeCode]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;b&amp;gt;Tutorials&amp;lt;/b&amp;gt;, these refer to the previous release but parts of them are still relevant.&lt;br /&gt;
* [[LLA Sandnet Tutorial]] - Setup Horizon using Sandnet and LLA&lt;br /&gt;
* [[LLA and Q Light Controller Ubuntu Tutorial]] - Setup LLA on Ubuntu/Debian-type distro with QLC&lt;br /&gt;
* [[LLA and Q Light Controller OSX Tutorial]] - Setup LLA on Mac OS X with QLC&lt;br /&gt;
&lt;br /&gt;
[[Category:ArtNet]]&lt;br /&gt;
[[Category:ESP Net]]&lt;br /&gt;
[[Category:E1.31]]&lt;br /&gt;
[[Category:Sandnet]]&lt;br /&gt;
[[Category:ShowNet]]&lt;br /&gt;
[[Category:Utilities]]&lt;br /&gt;
[[Category:Pathport]]&lt;/div&gt;</summary>
		<author><name>Nightrune</name></author>	</entry>

	<entry>
		<id>https://wiki.openlighting.org/index.php?title=Open_Lighting_Project&amp;diff=5497</id>
		<title>Open Lighting Project</title>
		<link rel="alternate" type="text/html" href="https://wiki.openlighting.org/index.php?title=Open_Lighting_Project&amp;diff=5497"/>
				<updated>2013-07-15T18:54:21Z</updated>
		
		<summary type="html">&lt;p&gt;Nightrune: Minor grammar edit.&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;The Open Lighting Project is a multi-faceted effort aimed at accelerating the adoption of new, standardized control protocols, while also providing high quality, reliable, open software for the lighting industry. This site acts as a resource for anyone looking for information about DMX software and the associated control systems, as well as a variety of Open Source and free lighting software.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;table style=&amp;quot;width: 100%; margin:4px 0 0 0; background:none; border-spacing: 5px;&amp;quot;&amp;gt;&lt;br /&gt;
 &amp;lt;tr&amp;gt;&lt;br /&gt;
  &amp;lt;td style=&amp;quot;width:45%; border:1px solid #cedff2; background:#f5faff; vertical-align:top; padding: 4px&amp;quot;&amp;gt;&lt;br /&gt;
    [[Image:OLA-Logo-Fitted-48px.png|right|link=OLA]]&lt;br /&gt;
    &amp;lt;h2 style=&amp;quot;float:left; font-size:120%; padding: .2em; margin:3px; font-weight:bold;&amp;quot;&amp;gt;[[OLA | The Open Lighting Architecture]]&amp;lt;/h2&amp;gt;&lt;br /&gt;
    &amp;lt;div style=&amp;quot;clear: left&amp;quot;&amp;gt;&lt;br /&gt;
The [[OLA | Open Lighting Architecture]] provides a framework for distributing lighting control information. It supports many protocols such as E1.31 (sACN), ArtNet, ShowNet, Pathport, RDM and over a dozen USB devices. It can run as a standalone service, which is useful for converting signals between protocols, or alternatively it can be used as the backend for [[:Category:Controllers | Controller Applications]]. OLA runs on a many different platforms including ARM, which makes it a perfect fit for low cost Ethernet to DMX gateways.&lt;br /&gt;
    &amp;lt;/div&amp;gt;&lt;br /&gt;
  &amp;lt;/td&amp;gt;&lt;br /&gt;
  &amp;lt;td style=&amp;quot;width:45%; border:1px solid #cedff2; background:#f5faff; vertical-align:top; padding: 4px&amp;quot;&amp;gt;&lt;br /&gt;
    [[Image:rdm-logo-small.png|right|link=]]&lt;br /&gt;
    &amp;lt;h2 style=&amp;quot;float:left; font-size:120%; padding: .2em; margin:3px; font-weight:bold;&amp;quot;&amp;gt;[[RDM_Responder_Testing | RDM Responder Tests]]&amp;lt;/h2&amp;gt;&lt;br /&gt;
    &amp;lt;div style=&amp;quot;clear: left&amp;quot;&amp;gt;&lt;br /&gt;
Testing RDM Responder used to involve manually sending commands and verifying the responses. Not any longer! The [[RDM_Responder_Testing | RDM Responder Tests]] automate all of this and provide a detailed breakdown of how well a responder complies with the [[E1.20]] (RDM) standard. This saves time during the product development process and raises the quality of RDM implementations across the industry.&lt;br /&gt;
&lt;br /&gt;
For questions about the RDM Responder tests, email the  [http://groups.google.com/group/rdm-testing RDM Testing List].&lt;br /&gt;
    &amp;lt;/div&amp;gt;&lt;br /&gt;
  &amp;lt;/td&amp;gt;&lt;br /&gt;
 &amp;lt;/tr&amp;gt;&lt;br /&gt;
 &amp;lt;tr&amp;gt;&amp;lt;td colspan=&amp;quot;2&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
 &amp;lt;tr&amp;gt;&lt;br /&gt;
  &amp;lt;td style=&amp;quot;width:45%; border:1px solid #cedff2; background:#f5faff; vertical-align:top; padding: 4px&amp;quot;&amp;gt;&lt;br /&gt;
    [[Image:raspi-logo-small.png|right|link=]]&lt;br /&gt;
    &amp;lt;h2 style=&amp;quot;float:left; font-size:120%; padding: .2em; margin:3px; font-weight:bold;&amp;quot;&amp;gt;[[OLA_Raspberry_Pi | OLA on the Raspberry Pi]]&amp;lt;/h2&amp;gt;&lt;br /&gt;
    &amp;lt;div style=&amp;quot;clear: left&amp;quot;&amp;gt;&lt;br /&gt;
The [http://www.raspberrypi.org/ Raspberry Pi] is one of the most popular platforms for running [[OLA]]. With the addition of a USB to DMX device, one can build a low cost, but fully functional Ethernet gateway. The [[OLA_Raspberry_Pi | OLA on Raspberry Pi]] tutorial has a step by step guide to installing OLA on the Pi.&lt;br /&gt;
    &amp;lt;/div&amp;gt;&lt;br /&gt;
  &amp;lt;/td&amp;gt;&lt;br /&gt;
&lt;br /&gt;
  &amp;lt;td style=&amp;quot;width:45%; border:1px solid #cedff2; background:#f5faff; vertical-align:top; padding: 4px&amp;quot;&amp;gt;&lt;br /&gt;
    [[Image:Robin-1200.png|right|link=]]&lt;br /&gt;
    &amp;lt;h2 style=&amp;quot;float:left; font-size:120%; padding: .2em; margin:3px; font-weight:bold;&amp;quot;&amp;gt;rdm.openlighting.org&amp;lt;/h2&amp;gt;&lt;br /&gt;
    &amp;lt;div style=&amp;quot;clear: left&amp;quot;&amp;gt;&lt;br /&gt;
The http://rdm.openlighting.org site contains an index of RDM-enabled products as well as the specifications for many of the manufacturer specific PIDs. The site has recently been expanded to display the results of the RDM Responder Tests. The data on the site is available free of charge through APIs. &lt;br /&gt;
    &amp;lt;/div&amp;gt;&lt;br /&gt;
  &amp;lt;/td&amp;gt;&lt;br /&gt;
 &amp;lt;/tr&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td colspan=&amp;quot;2&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
 &amp;lt;tr&amp;gt;&lt;br /&gt;
  &amp;lt;td style=&amp;quot;width:45%; border:1px solid #cedff2; background:#f5faff; vertical-align:top; padding: 4px&amp;quot;&amp;gt;&lt;br /&gt;
    [[Image:Email-icon.png|right|link=]]&lt;br /&gt;
    &amp;lt;h2 style=&amp;quot;float:left; font-size:120%; padding: .2em; margin:3px; font-weight:bold;&amp;quot;&amp;gt;Contact / Support&amp;lt;/h2&amp;gt;&lt;br /&gt;
    &amp;lt;div style=&amp;quot;clear: left&amp;quot;&amp;gt;&lt;br /&gt;
Since this is an Open Source project, there is no commercial support for our products at this time. There are a number of ways of reaching the community though:&lt;br /&gt;
&lt;br /&gt;
* Primary User &amp;amp; Developer Discussion [http://groups.google.com/group/open-lighting Open Lighting Discuss] (typically a few messages per day).&lt;br /&gt;
* Announcements are posted to [http://groups.google.com/group/open-lighting-announce Open Lighting Announce] (low volume, typically 1-2 per month)&lt;br /&gt;
* RDM Testing Discussion [http://groups.google.com/group/rdm-testing RDM Testing].&lt;br /&gt;
* IRC #openlighting on freenode.net (or [http://webchat.freenode.net/?channels=openlighting webchat])&lt;br /&gt;
There is also an [https://plus.google.com/106460627923808853381 Open Lighting Community] on Google+. This is less OLA centric and more about sharing cool lighting projects people are working on.&lt;br /&gt;
    &amp;lt;/div&amp;gt;&lt;br /&gt;
  &amp;lt;/td&amp;gt;&lt;br /&gt;
&lt;br /&gt;
  &amp;lt;td style=&amp;quot;width:45%; border:1px solid #cedff2; background:#f5faff; vertical-align:top; padding: 4px&amp;quot;&amp;gt;&lt;br /&gt;
    &amp;lt;h2 style=&amp;quot;float:left; font-size:120%; padding: .2em; margin:3px; font-weight:bold;&amp;quot;&amp;gt;Other Projects&amp;lt;/h2&amp;gt;&lt;br /&gt;
    &amp;lt;div style=&amp;quot;clear: left&amp;quot;&amp;gt;&lt;br /&gt;
* [[libartnet]]. The library that started it all, libartnet is an [[ArtNet]] implementation for Mac, Linux and Windows &amp;amp; iPhone.&lt;br /&gt;
* [[Logic RDM Sniffer]] - Use a [http://saleae.com/logic Saleae Logic] device as a RDM analyser. &lt;br /&gt;
* [[Arduino RGB Mixer]], open source firmware for Arduinos, so that they can be used as a simple RGB Color Mixer. Now with RDM support!&lt;br /&gt;
* [[OLA_DMX_Trigger | DMX Trigger]], this can execute command line programs based on DMX values. It's useful for building DMX controlled media players.&lt;br /&gt;
* [[E1.33 SLP SA Tests]], similar to the RDM Responder Tests, this performs tests against a RDMNet Device's SLP implementation.&lt;br /&gt;
* [[OLA LED Pixels]], drive pixel strings using OLA&lt;br /&gt;
    &amp;lt;/div&amp;gt;&lt;br /&gt;
  &amp;lt;/td&amp;gt;&lt;br /&gt;
 &amp;lt;/tr&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td colspan=&amp;quot;2&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
 &amp;lt;tr&amp;gt;&lt;br /&gt;
  &amp;lt;td style=&amp;quot;width:45%; border:1px solid #cedff2; background:#f5faff; vertical-align:top; padding: 4px&amp;quot;&amp;gt;&lt;br /&gt;
    &amp;lt;h2 style=&amp;quot;float:left; font-size:120%; padding: .2em; margin:3px; font-weight:bold;&amp;quot;&amp;gt;Project Supporters&amp;lt;/h2&amp;gt;&lt;br /&gt;
    &amp;lt;div style=&amp;quot;clear: left&amp;quot;&amp;gt;&lt;br /&gt;
Many individuals &amp;amp; organizations have supported the project over the years. We're grateful to all of them.&lt;br /&gt;
&lt;br /&gt;
* [http://www.anyma.ch Anyma], provided a [[Anyma_uDMX|uDMX]]&lt;br /&gt;
* [[Artistic Licence]], provided a [[Net-Lynx]] &amp;amp; Down-Lynx for Art-Net / RDM testing and a [[Rail-Tran]] to test [[RDM]] support&lt;br /&gt;
* Andrew Frazer, who sponsored the development of ola_trigger with a [[RDM USB Pro]] &lt;br /&gt;
* [http://www.creativelighting.com.au/ Creative Lighting], provided a [[SLAMMO XC-1]] &amp;amp; [[ADDICT]] for [[RDM]] testing.&lt;br /&gt;
* [[Enttec]], provided a [[DMX USB Pro]]&lt;br /&gt;
* Eric Johnson, for hosting the server used to test &amp;amp; debug much of the RDM code.&lt;br /&gt;
* Florian from eventa.ag who donated a [[StageProfi]] and a [[USBDMX2]]&lt;br /&gt;
* [http://www.goddarddesign.com/ Goddard Design], who made available a  [[MiniDMXter]]&lt;br /&gt;
* Jason Kyle from [http://www.DMXking.com DMXKing.com] provided a [[DMXking USB DMX512-A]]&lt;br /&gt;
* [[JESE]], provided a [[DMX-TRI]] &amp;amp;  [[RDM-TRI]] &amp;amp; Tempest Enclosure to test the RDM implementation. &lt;br /&gt;
* [http://www.ljusdesign.se LjusDesign AB] who donated 7 RDM splitters.&lt;br /&gt;
* [http://www.lumenradio.com/ LumenRadio] who provided a Nova TX2 RDM, Nova RX RDM and Nova FX units and a Raspberry Pi.&lt;br /&gt;
* [http://www.martin.com Martin Professional A/S] which loaned a Mac 700 for RDM testing &lt;br /&gt;
* [http://www.milinst.co.uk/ Milford Instruments] who sent 3 RDMChips for testing.&lt;br /&gt;
* Peter Kirkup, from [http://www.zero88.com/ Zero 88] who donated a Betapack 3&lt;br /&gt;
* Petr from [[ROBE Lighting]] who loaned a [[Robe Universal Interface]] and [http://www.robe.cz/products/article/robin-600e-spot/ Robin 600]&lt;br /&gt;
* [http://www.sandsys.com/ Sandsys], donated a [http://www.sandsys.com/products/SB-AAA2100.htm SandBox]&lt;br /&gt;
* Shaun Jackman, answered questions about the [[:Category:Pathport|Pathport]] Protocol&lt;br /&gt;
* [http://soundlight.de/ SoundLight] who loaned a 3604PWM-H device&lt;br /&gt;
* [http://www.waapa.ecu.edu.au West Australian Academy of Performing Arts] (WAAPA) for access to a [[Strand Lighting]] console.&lt;br /&gt;
&lt;br /&gt;
    &amp;lt;/div&amp;gt;&lt;br /&gt;
  &amp;lt;/td&amp;gt;&lt;br /&gt;
&lt;br /&gt;
  &amp;lt;td style=&amp;quot;width:45%; border:1px solid #cedff2; background:#f5faff; vertical-align:top; padding: 4px&amp;quot;&amp;gt;&lt;br /&gt;
    &amp;lt;h2 style=&amp;quot;float:left; font-size:120%; padding: .2em; margin:3px; font-weight:bold;&amp;quot;&amp;gt;Get Involved&amp;lt;/h2&amp;gt;&lt;br /&gt;
    &amp;lt;div style=&amp;quot;clear: left&amp;quot;&amp;gt;&lt;br /&gt;
There is plenty of opportunity to get involved. If you would like to help with any of the following (or have your own ideas) then please get in touch with us on the [http://groups.google.com/group/open-lighting Open Lighting Group]&lt;br /&gt;
&lt;br /&gt;
* Technical Writers, the documentation could do with some cleanup.&lt;br /&gt;
* Packagers, we need people to build binary packages for Mac, Debian/Ubuntu and RPM-based distros&lt;br /&gt;
* Windows programmers, are you interested in helping [[Building_OLA_for_Windows| port OLA to Windows]]?  &lt;br /&gt;
* Java programmers, we need someone to write the Java client API [http://code.google.com/p/linux-lighting/issues/detail?id=15 ]&lt;br /&gt;
* Equipment donation, do you own or know of a [[:Category:USB | USB interface]] or RDM device we don't support yet? Consider lending it to us.&lt;br /&gt;
* Web designers, the web UI could do with a facelift.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The programming team behind OLA consists of:&lt;br /&gt;
* Bastien Andrès, contributed to the dmx4linux plugin&lt;br /&gt;
* Harry F, for the Eurolite USB Pro code&lt;br /&gt;
* Heikki Junnila, bug fixes for the debian packaging files&lt;br /&gt;
* Laurent  (Renzo), Debian packages, FreeBSD &amp;amp; RDM testing.&lt;br /&gt;
* Masaki Muranaka, various patches&lt;br /&gt;
* Nicolas, for the win32 port of libartnet&lt;br /&gt;
* Ravindra Nath Kakarla, RDM Test Server (Part of [http://www.google-melange.com/gsoc/profile/organization/google/gsoc2012/openlighting Google Summer of Code 2012] ).&lt;br /&gt;
* Rowan Maclachlan (hippy) for various changes&lt;br /&gt;
* Rui Barreiros for the FTDI plugin&lt;br /&gt;
* Tobi Schäfer, for the MacPort files&lt;br /&gt;
    &amp;lt;/div&amp;gt;&lt;br /&gt;
  &amp;lt;/td&amp;gt;&lt;br /&gt;
 &amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;/table&amp;gt;&lt;br /&gt;
&lt;br /&gt;
__NOTOC__&lt;/div&gt;</summary>
		<author><name>Nightrune</name></author>	</entry>

	<entry>
		<id>https://wiki.openlighting.org/index.php?title=Open_Lighting_Project&amp;diff=5496</id>
		<title>Open Lighting Project</title>
		<link rel="alternate" type="text/html" href="https://wiki.openlighting.org/index.php?title=Open_Lighting_Project&amp;diff=5496"/>
				<updated>2013-07-15T18:51:44Z</updated>
		
		<summary type="html">&lt;p&gt;Nightrune: Minor capitalization changes&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;The Open Lighting Project is a multi-faceted effort aimed at accelerating the adoption of new, standardized control protocols, while also providing high quality, reliable, open software for the lighting industry. This site acts as a resource for anyone looking for information about DMX software and the associated control systems, as well as a variety of Open Source and free lighting software.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;table style=&amp;quot;width: 100%; margin:4px 0 0 0; background:none; border-spacing: 5px;&amp;quot;&amp;gt;&lt;br /&gt;
 &amp;lt;tr&amp;gt;&lt;br /&gt;
  &amp;lt;td style=&amp;quot;width:45%; border:1px solid #cedff2; background:#f5faff; vertical-align:top; padding: 4px&amp;quot;&amp;gt;&lt;br /&gt;
    [[Image:OLA-Logo-Fitted-48px.png|right|link=OLA]]&lt;br /&gt;
    &amp;lt;h2 style=&amp;quot;float:left; font-size:120%; padding: .2em; margin:3px; font-weight:bold;&amp;quot;&amp;gt;[[OLA | The Open Lighting Architecture]]&amp;lt;/h2&amp;gt;&lt;br /&gt;
    &amp;lt;div style=&amp;quot;clear: left&amp;quot;&amp;gt;&lt;br /&gt;
The [[OLA | Open Lighting Architecture]] provides a framework for distributing lighting control information. It supports many protocols such as E1.31 (sACN), ArtNet, ShowNet, Pathport &amp;amp; RDM and over a dozen USB devices. It can run as a standalone service, which is useful for converting signals between protocols, or alternatively it can be used as the backend for [[:Category:Controllers | Controller Applications]]. OLA runs on a many different platforms including ARM, which makes it a perfect fit for low cost Ethernet to DMX gateways.&lt;br /&gt;
    &amp;lt;/div&amp;gt;&lt;br /&gt;
  &amp;lt;/td&amp;gt;&lt;br /&gt;
  &amp;lt;td style=&amp;quot;width:45%; border:1px solid #cedff2; background:#f5faff; vertical-align:top; padding: 4px&amp;quot;&amp;gt;&lt;br /&gt;
    [[Image:rdm-logo-small.png|right|link=]]&lt;br /&gt;
    &amp;lt;h2 style=&amp;quot;float:left; font-size:120%; padding: .2em; margin:3px; font-weight:bold;&amp;quot;&amp;gt;[[RDM_Responder_Testing | RDM Responder Tests]]&amp;lt;/h2&amp;gt;&lt;br /&gt;
    &amp;lt;div style=&amp;quot;clear: left&amp;quot;&amp;gt;&lt;br /&gt;
Testing RDM Responder used to involve manually sending commands and verifying the responses. Not any longer! The [[RDM_Responder_Testing | RDM Responder Tests]] automate all of this and provide a detailed breakdown of how well a responder complies with the [[E1.20]] (RDM) standard. This saves time during the product development process and raises the quality of RDM implementations across the industry.&lt;br /&gt;
&lt;br /&gt;
For questions about the RDM Responder tests, email the  [http://groups.google.com/group/rdm-testing RDM Testing List].&lt;br /&gt;
    &amp;lt;/div&amp;gt;&lt;br /&gt;
  &amp;lt;/td&amp;gt;&lt;br /&gt;
 &amp;lt;/tr&amp;gt;&lt;br /&gt;
 &amp;lt;tr&amp;gt;&amp;lt;td colspan=&amp;quot;2&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
 &amp;lt;tr&amp;gt;&lt;br /&gt;
  &amp;lt;td style=&amp;quot;width:45%; border:1px solid #cedff2; background:#f5faff; vertical-align:top; padding: 4px&amp;quot;&amp;gt;&lt;br /&gt;
    [[Image:raspi-logo-small.png|right|link=]]&lt;br /&gt;
    &amp;lt;h2 style=&amp;quot;float:left; font-size:120%; padding: .2em; margin:3px; font-weight:bold;&amp;quot;&amp;gt;[[OLA_Raspberry_Pi | OLA on the Raspberry Pi]]&amp;lt;/h2&amp;gt;&lt;br /&gt;
    &amp;lt;div style=&amp;quot;clear: left&amp;quot;&amp;gt;&lt;br /&gt;
The [http://www.raspberrypi.org/ Raspberry Pi] is one of the most popular platforms for running [[OLA]]. With the addition of a USB to DMX device, one can build a low cost, but fully functional Ethernet gateway. The [[OLA_Raspberry_Pi | OLA on Raspberry Pi]] tutorial has a step by step guide to installing OLA on the Pi.&lt;br /&gt;
    &amp;lt;/div&amp;gt;&lt;br /&gt;
  &amp;lt;/td&amp;gt;&lt;br /&gt;
&lt;br /&gt;
  &amp;lt;td style=&amp;quot;width:45%; border:1px solid #cedff2; background:#f5faff; vertical-align:top; padding: 4px&amp;quot;&amp;gt;&lt;br /&gt;
    [[Image:Robin-1200.png|right|link=]]&lt;br /&gt;
    &amp;lt;h2 style=&amp;quot;float:left; font-size:120%; padding: .2em; margin:3px; font-weight:bold;&amp;quot;&amp;gt;rdm.openlighting.org&amp;lt;/h2&amp;gt;&lt;br /&gt;
    &amp;lt;div style=&amp;quot;clear: left&amp;quot;&amp;gt;&lt;br /&gt;
The http://rdm.openlighting.org site contains an index of RDM-enabled products as well as the specifications for many of the manufacturer specific PIDs. The site has recently been expanded to display the results of the RDM Responder Tests. The data on the site is available free of charge through APIs. &lt;br /&gt;
    &amp;lt;/div&amp;gt;&lt;br /&gt;
  &amp;lt;/td&amp;gt;&lt;br /&gt;
 &amp;lt;/tr&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td colspan=&amp;quot;2&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
 &amp;lt;tr&amp;gt;&lt;br /&gt;
  &amp;lt;td style=&amp;quot;width:45%; border:1px solid #cedff2; background:#f5faff; vertical-align:top; padding: 4px&amp;quot;&amp;gt;&lt;br /&gt;
    [[Image:Email-icon.png|right|link=]]&lt;br /&gt;
    &amp;lt;h2 style=&amp;quot;float:left; font-size:120%; padding: .2em; margin:3px; font-weight:bold;&amp;quot;&amp;gt;Contact / Support&amp;lt;/h2&amp;gt;&lt;br /&gt;
    &amp;lt;div style=&amp;quot;clear: left&amp;quot;&amp;gt;&lt;br /&gt;
Since this is an Open Source project, there is no commercial support for our products at this time. There are a number of ways of reaching the community though:&lt;br /&gt;
&lt;br /&gt;
* Primary User &amp;amp; Developer Discussion [http://groups.google.com/group/open-lighting Open Lighting Discuss] (typically a few messages per day).&lt;br /&gt;
* Announcements are posted to [http://groups.google.com/group/open-lighting-announce Open Lighting Announce] (low volume, typically 1-2 per month)&lt;br /&gt;
* RDM Testing Discussion [http://groups.google.com/group/rdm-testing RDM Testing].&lt;br /&gt;
* IRC #openlighting on freenode.net (or [http://webchat.freenode.net/?channels=openlighting webchat])&lt;br /&gt;
There is also an [https://plus.google.com/106460627923808853381 Open Lighting Community] on Google+. This is less OLA centric and more about sharing cool lighting projects people are working on.&lt;br /&gt;
    &amp;lt;/div&amp;gt;&lt;br /&gt;
  &amp;lt;/td&amp;gt;&lt;br /&gt;
&lt;br /&gt;
  &amp;lt;td style=&amp;quot;width:45%; border:1px solid #cedff2; background:#f5faff; vertical-align:top; padding: 4px&amp;quot;&amp;gt;&lt;br /&gt;
    &amp;lt;h2 style=&amp;quot;float:left; font-size:120%; padding: .2em; margin:3px; font-weight:bold;&amp;quot;&amp;gt;Other Projects&amp;lt;/h2&amp;gt;&lt;br /&gt;
    &amp;lt;div style=&amp;quot;clear: left&amp;quot;&amp;gt;&lt;br /&gt;
* [[libartnet]]. The library that started it all, libartnet is an [[ArtNet]] implementation for Mac, Linux and Windows &amp;amp; iPhone.&lt;br /&gt;
* [[Logic RDM Sniffer]] - Use a [http://saleae.com/logic Saleae Logic] device as a RDM analyser. &lt;br /&gt;
* [[Arduino RGB Mixer]], open source firmware for Arduinos, so that they can be used as a simple RGB Color Mixer. Now with RDM support!&lt;br /&gt;
* [[OLA_DMX_Trigger | DMX Trigger]], this can execute command line programs based on DMX values. It's useful for building DMX controlled media players.&lt;br /&gt;
* [[E1.33 SLP SA Tests]], similar to the RDM Responder Tests, this performs tests against a RDMNet Device's SLP implementation.&lt;br /&gt;
* [[OLA LED Pixels]], drive pixel strings using OLA&lt;br /&gt;
    &amp;lt;/div&amp;gt;&lt;br /&gt;
  &amp;lt;/td&amp;gt;&lt;br /&gt;
 &amp;lt;/tr&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td colspan=&amp;quot;2&amp;quot;&amp;gt;&amp;amp;nbsp;&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
 &amp;lt;tr&amp;gt;&lt;br /&gt;
  &amp;lt;td style=&amp;quot;width:45%; border:1px solid #cedff2; background:#f5faff; vertical-align:top; padding: 4px&amp;quot;&amp;gt;&lt;br /&gt;
    &amp;lt;h2 style=&amp;quot;float:left; font-size:120%; padding: .2em; margin:3px; font-weight:bold;&amp;quot;&amp;gt;Project Supporters&amp;lt;/h2&amp;gt;&lt;br /&gt;
    &amp;lt;div style=&amp;quot;clear: left&amp;quot;&amp;gt;&lt;br /&gt;
Many individuals &amp;amp; organizations have supported the project over the years. We're grateful to all of them.&lt;br /&gt;
&lt;br /&gt;
* [http://www.anyma.ch Anyma], provided a [[Anyma_uDMX|uDMX]]&lt;br /&gt;
* [[Artistic Licence]], provided a [[Net-Lynx]] &amp;amp; Down-Lynx for Art-Net / RDM testing and a [[Rail-Tran]] to test [[RDM]] support&lt;br /&gt;
* Andrew Frazer, who sponsored the development of ola_trigger with a [[RDM USB Pro]] &lt;br /&gt;
* [http://www.creativelighting.com.au/ Creative Lighting], provided a [[SLAMMO XC-1]] &amp;amp; [[ADDICT]] for [[RDM]] testing.&lt;br /&gt;
* [[Enttec]], provided a [[DMX USB Pro]]&lt;br /&gt;
* Eric Johnson, for hosting the server used to test &amp;amp; debug much of the RDM code.&lt;br /&gt;
* Florian from eventa.ag who donated a [[StageProfi]] and a [[USBDMX2]]&lt;br /&gt;
* [http://www.goddarddesign.com/ Goddard Design], who made available a  [[MiniDMXter]]&lt;br /&gt;
* Jason Kyle from [http://www.DMXking.com DMXKing.com] provided a [[DMXking USB DMX512-A]]&lt;br /&gt;
* [[JESE]], provided a [[DMX-TRI]] &amp;amp;  [[RDM-TRI]] &amp;amp; Tempest Enclosure to test the RDM implementation. &lt;br /&gt;
* [http://www.ljusdesign.se LjusDesign AB] who donated 7 RDM splitters.&lt;br /&gt;
* [http://www.lumenradio.com/ LumenRadio] who provided a Nova TX2 RDM, Nova RX RDM and Nova FX units and a Raspberry Pi.&lt;br /&gt;
* [http://www.martin.com Martin Professional A/S] which loaned a Mac 700 for RDM testing &lt;br /&gt;
* [http://www.milinst.co.uk/ Milford Instruments] who sent 3 RDMChips for testing.&lt;br /&gt;
* Peter Kirkup, from [http://www.zero88.com/ Zero 88] who donated a Betapack 3&lt;br /&gt;
* Petr from [[ROBE Lighting]] who loaned a [[Robe Universal Interface]] and [http://www.robe.cz/products/article/robin-600e-spot/ Robin 600]&lt;br /&gt;
* [http://www.sandsys.com/ Sandsys], donated a [http://www.sandsys.com/products/SB-AAA2100.htm SandBox]&lt;br /&gt;
* Shaun Jackman, answered questions about the [[:Category:Pathport|Pathport]] Protocol&lt;br /&gt;
* [http://soundlight.de/ SoundLight] who loaned a 3604PWM-H device&lt;br /&gt;
* [http://www.waapa.ecu.edu.au West Australian Academy of Performing Arts] (WAAPA) for access to a [[Strand Lighting]] console.&lt;br /&gt;
&lt;br /&gt;
    &amp;lt;/div&amp;gt;&lt;br /&gt;
  &amp;lt;/td&amp;gt;&lt;br /&gt;
&lt;br /&gt;
  &amp;lt;td style=&amp;quot;width:45%; border:1px solid #cedff2; background:#f5faff; vertical-align:top; padding: 4px&amp;quot;&amp;gt;&lt;br /&gt;
    &amp;lt;h2 style=&amp;quot;float:left; font-size:120%; padding: .2em; margin:3px; font-weight:bold;&amp;quot;&amp;gt;Get Involved&amp;lt;/h2&amp;gt;&lt;br /&gt;
    &amp;lt;div style=&amp;quot;clear: left&amp;quot;&amp;gt;&lt;br /&gt;
There is plenty of opportunity to get involved. If you would like to help with any of the following (or have your own ideas) then please get in touch with us on the [http://groups.google.com/group/open-lighting Open Lighting Group]&lt;br /&gt;
&lt;br /&gt;
* Technical Writers, the documentation could do with some cleanup.&lt;br /&gt;
* Packagers, we need people to build binary packages for Mac, Debian/Ubuntu and RPM-based distros&lt;br /&gt;
* Windows programmers, are you interested in helping [[Building_OLA_for_Windows| port OLA to Windows]]?  &lt;br /&gt;
* Java programmers, we need someone to write the Java client API [http://code.google.com/p/linux-lighting/issues/detail?id=15 ]&lt;br /&gt;
* Equipment donation, do you own or know of a [[:Category:USB | USB interface]] or RDM device we don't support yet? Consider lending it to us.&lt;br /&gt;
* Web designers, the web UI could do with a facelift.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The programming team behind OLA consists of:&lt;br /&gt;
* Bastien Andrès, contributed to the dmx4linux plugin&lt;br /&gt;
* Harry F, for the Eurolite USB Pro code&lt;br /&gt;
* Heikki Junnila, bug fixes for the debian packaging files&lt;br /&gt;
* Laurent  (Renzo), Debian packages, FreeBSD &amp;amp; RDM testing.&lt;br /&gt;
* Masaki Muranaka, various patches&lt;br /&gt;
* Nicolas, for the win32 port of libartnet&lt;br /&gt;
* Ravindra Nath Kakarla, RDM Test Server (Part of [http://www.google-melange.com/gsoc/profile/organization/google/gsoc2012/openlighting Google Summer of Code 2012] ).&lt;br /&gt;
* Rowan Maclachlan (hippy) for various changes&lt;br /&gt;
* Rui Barreiros for the FTDI plugin&lt;br /&gt;
* Tobi Schäfer, for the MacPort files&lt;br /&gt;
    &amp;lt;/div&amp;gt;&lt;br /&gt;
  &amp;lt;/td&amp;gt;&lt;br /&gt;
 &amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;/table&amp;gt;&lt;br /&gt;
&lt;br /&gt;
__NOTOC__&lt;/div&gt;</summary>
		<author><name>Nightrune</name></author>	</entry>

	<entry>
		<id>https://wiki.openlighting.org/index.php?title=OLA_on_Linux&amp;diff=5361</id>
		<title>OLA on Linux</title>
		<link rel="alternate" type="text/html" href="https://wiki.openlighting.org/index.php?title=OLA_on_Linux&amp;diff=5361"/>
				<updated>2013-06-02T19:50:26Z</updated>
		
		<summary type="html">&lt;p&gt;Nightrune: Nevermind I was on an old version of ubuntu&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This describes how to get [[OLA]] working on a Linux system either from the git repo or by using a [http://code.google.com/p/open-lighting/downloads/list released tarball].&lt;br /&gt;
&lt;br /&gt;
=Install dependencies =&lt;br /&gt;
&lt;br /&gt;
You need a couple of libraries installed for everything to work correctly. Some of these are available as packages in distros but others need to be downloaded and built manually.&lt;br /&gt;
&lt;br /&gt;
First you'll need at least the following:&lt;br /&gt;
* cppunit&lt;br /&gt;
* uuid or ossp uuid&lt;br /&gt;
* pkg-config&lt;br /&gt;
* curses&lt;br /&gt;
* lex (or flex)&lt;br /&gt;
* yacc (or bison)&lt;br /&gt;
* the protocol buffers library   [http://code.google.com/p/protobuf/ http://code.google.com/p/protobuf/] (version 2.3.0 or later)&lt;br /&gt;
* microhttpd  [ftp://ftp.gnu.org/gnu/libmicrohttpd/ ftp://ftp.gnu.org/gnu/libmicrohttpd/] (if you want the web UI). You need version &amp;gt;= 0.4.0 of microhttpd&lt;br /&gt;
&lt;br /&gt;
If you're building from git you'll also need the following:&lt;br /&gt;
&lt;br /&gt;
* libtool&lt;br /&gt;
* automake&lt;br /&gt;
* autoconf&lt;br /&gt;
&lt;br /&gt;
== Debian / Ubuntu ==&lt;br /&gt;
There is a fully packaged version of OLA you can just install, for info see [[OLA Debian / Ubuntu]]. There's also a more specific Ubuntu walkthrough for building [[The Newbie Guide for OLA on Ubuntu]].&lt;br /&gt;
&lt;br /&gt;
Debian/Ubuntu users can install them with apt:&lt;br /&gt;
&lt;br /&gt;
  sudo apt-get install libcppunit-dev libcppunit-1.12-1 uuid-dev pkg-config libncurses5-dev libtool autoconf automake  g++ libmicrohttpd-dev \&lt;br /&gt;
  libmicrohttpd10 protobuf-compiler libprotobuf-lite7 python-protobuf libprotobuf-dev zlib1g-dev bison flex make libftdi-dev  libftdi1 libusb-1.0-0-dev liblo-dev &lt;br /&gt;
&lt;br /&gt;
Note: Some distributions may offer libprotobuf-lite6 instead of libprotobuf-lite7, which is an acceptable substitution.&lt;br /&gt;
&lt;br /&gt;
If you're using Ubuntu 12.04 or later you can just use the command above. In earlier versions of Ubuntu the version of libprotobuf is too old, so you'll need to install them by hand. You may also need to install an older version of libmicrohttpd (libmicrohttpd9 rather than libmicrohttpd10).&lt;br /&gt;
&lt;br /&gt;
== Centos 6 / RHEL 6 / Fedora 17 ==&lt;br /&gt;
&lt;br /&gt;
Users of rpm based distributions can install them with yum (protobuf*, libmicrohttpd* and libftdi* are in the EPEL repository):&lt;br /&gt;
&lt;br /&gt;
  sudo yum install flex bison protobuf protobuf-devel uuid-devel cppunit-devel protobuf-python libmicrohttpd-devel libusb-devel libftdi-devel libuuid-devel openslp-devel&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
(The remaining libs already come with the OS installation)&lt;br /&gt;
&lt;br /&gt;
== Other Distributions ==&lt;br /&gt;
&lt;br /&gt;
Install using your package manager, or build everything by hand&lt;br /&gt;
&lt;br /&gt;
If you installed things by hand (rather than using your package manager), you need to run ldconfig as root to pick up the new libraries&lt;br /&gt;
&lt;br /&gt;
  sudo  ldconfig&lt;br /&gt;
&lt;br /&gt;
=Checkout or Download an Archive=&lt;br /&gt;
&lt;br /&gt;
You can either download a tarball, or pull the latest version from the git repo&lt;br /&gt;
&lt;br /&gt;
== Tarball ==&lt;br /&gt;
&lt;br /&gt;
Download the most recent tarball from http://code.google.com/p/open-lighting/downloads/list&lt;br /&gt;
Extract using&lt;br /&gt;
&lt;br /&gt;
  tar -zxf ola-0.X.Y.tar.gz&lt;br /&gt;
  cd ola-0.X.Y&lt;br /&gt;
&lt;br /&gt;
== Git ==&lt;br /&gt;
&lt;br /&gt;
If you don't have '''git''' yet, you'll need to install it with your distro's package manager. On Debian / Ubuntu run:&lt;br /&gt;
&lt;br /&gt;
  sudo apt-get install git&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Check out the git repo with the following command:&lt;br /&gt;
&lt;br /&gt;
  git clone https://code.google.com/p/open-lighting/ ola&lt;br /&gt;
  cd ola&lt;br /&gt;
&lt;br /&gt;
{{ MacOLABuild }}&lt;br /&gt;
&lt;br /&gt;
Finally run ldconfig so you can use the new libraries.&lt;br /&gt;
&lt;br /&gt;
  sudo ldconfig&lt;br /&gt;
&lt;br /&gt;
=Device drivers=&lt;br /&gt;
Note that, for some devices, it is necessary to install drivers for OLA to work with them. For example, the [[Open DMX USB]] device needs an additional kernel module that could be built using the instuctions on [[LLA_and_Q_Light_Controller_Ubuntu_Tutorial]]. For other devices, refer to the corresponding device page on this wiki.&lt;br /&gt;
&lt;br /&gt;
=Known Issues=&lt;br /&gt;
&lt;br /&gt;
If you get an error like the following:&lt;br /&gt;
&lt;br /&gt;
 /bin/sh ./libtool --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I.   -I/opt/local/var/macports/software/protobuf-cpp/2.0.3_0/opt/local/include/  -g -O2 -c -o ltdl.lo ltdl.c&lt;br /&gt;
 ./libtool: line 464: CDPATH: command not found&lt;br /&gt;
 /Users/simonn/lighting/lla/libltdl/libtool: line 464: CDPATH: command not found&lt;br /&gt;
 /Users/simonn/lighting/lla/libltdl/libtool: line 1142: func_opt_split: command not found&lt;br /&gt;
 libtool: Version mismatch error.  This is libtool 2.2.6, but the&lt;br /&gt;
 libtool: definition of this LT_INIT comes from an older release.&lt;br /&gt;
 libtool: You should recreate aclocal.m4 with macros from libtool 2.2.6&lt;br /&gt;
 libtool: and run autoconf again.&lt;br /&gt;
&lt;br /&gt;
Your system uses a different version of libtool. Run:&lt;br /&gt;
&lt;br /&gt;
  libtoolize --ltdl -c -f&lt;br /&gt;
&lt;br /&gt;
and then start from the autoreconf step again.&lt;br /&gt;
&lt;br /&gt;
If you should get the following error try to fix it with one of [http://groups.google.com/group/open-lighting/msg/72060f6327d30df6 two available solutions]:&lt;br /&gt;
&lt;br /&gt;
 Rpc.pb.cc: In copy constructor 'ola::rpc::RpcMessage::RpcMessage(const ola::rpc::RpcMessage&amp;amp;)': &lt;br /&gt;
 Rpc.pb.cc:143: error: base class 'class google::protobuf::Message' should be explicitly initialized in the copy constructor &lt;br /&gt;
&lt;br /&gt;
You should be able to prevent this by [http://groups.google.com/group/open-lighting/msg/c6d86d03dd74ed5b editing &amp;lt;code&amp;gt;./src/Makefile.am&amp;lt;/code&amp;gt;], removing &amp;lt;code&amp;gt;-Werror&amp;lt;/code&amp;gt; and then start from the autoreconfig step again.&lt;/div&gt;</summary>
		<author><name>Nightrune</name></author>	</entry>

	<entry>
		<id>https://wiki.openlighting.org/index.php?title=OLA_on_Linux&amp;diff=5360</id>
		<title>OLA on Linux</title>
		<link rel="alternate" type="text/html" href="https://wiki.openlighting.org/index.php?title=OLA_on_Linux&amp;diff=5360"/>
				<updated>2013-06-01T22:17:03Z</updated>
		
		<summary type="html">&lt;p&gt;Nightrune: The build command failed when I tried the original. libmircohttpd10 isn't a real package.&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This describes how to get [[OLA]] working on a Linux system either from the git repo or by using a [http://code.google.com/p/open-lighting/downloads/list released tarball].&lt;br /&gt;
&lt;br /&gt;
=Install dependencies =&lt;br /&gt;
&lt;br /&gt;
You need a couple of libraries installed for everything to work correctly. Some of these are available as packages in distros but others need to be downloaded and built manually.&lt;br /&gt;
&lt;br /&gt;
First you'll need at least the following:&lt;br /&gt;
* cppunit&lt;br /&gt;
* uuid or ossp uuid&lt;br /&gt;
* pkg-config&lt;br /&gt;
* curses&lt;br /&gt;
* lex (or flex)&lt;br /&gt;
* yacc (or bison)&lt;br /&gt;
* the protocol buffers library   [http://code.google.com/p/protobuf/ http://code.google.com/p/protobuf/] (version 2.3.0 or later)&lt;br /&gt;
* microhttpd  [ftp://ftp.gnu.org/gnu/libmicrohttpd/ ftp://ftp.gnu.org/gnu/libmicrohttpd/] (if you want the web UI). You need version &amp;gt;= 0.4.0 of microhttpd&lt;br /&gt;
&lt;br /&gt;
If you're building from git you'll also need the following:&lt;br /&gt;
&lt;br /&gt;
* libtool&lt;br /&gt;
* automake&lt;br /&gt;
* autoconf&lt;br /&gt;
&lt;br /&gt;
== Debian / Ubuntu ==&lt;br /&gt;
There is a fully packaged version of OLA you can just install, for info see [[OLA Debian / Ubuntu]]. There's also a more specific Ubuntu walkthrough for building [[The Newbie Guide for OLA on Ubuntu]].&lt;br /&gt;
&lt;br /&gt;
Debian/Ubuntu users can install them with apt:&lt;br /&gt;
&lt;br /&gt;
  sudo apt-get install libcppunit-dev libcppunit-1.12-1 uuid-dev pkg-config libncurses5-dev libtool autoconf automake  g++ libmicrohttpd-dev \&lt;br /&gt;
  libmicrohttpd5 protobuf-compiler libprotobuf-lite7 python-protobuf libprotobuf-dev zlib1g-dev bison flex make libftdi-dev  libftdi1 libusb-1.0-0-dev liblo-dev &lt;br /&gt;
&lt;br /&gt;
Note: Some distributions may offer libprotobuf-lite6 instead of libprotobuf-lite7, which is an acceptable substitution.&lt;br /&gt;
&lt;br /&gt;
If you're using Ubuntu 12.04 or later you can just use the command above. In earlier versions of Ubuntu the version of libprotobuf is too old, so you'll need to install them by hand. You may also need to install an older version of libmicrohttpd (libmicrohttpd9 rather than libmicrohttpd10).&lt;br /&gt;
&lt;br /&gt;
== Centos 6 / RHEL 6 / Fedora 17 ==&lt;br /&gt;
&lt;br /&gt;
Users of rpm based distributions can install them with yum (protobuf*, libmicrohttpd* and libftdi* are in the EPEL repository):&lt;br /&gt;
&lt;br /&gt;
  sudo yum install flex bison protobuf protobuf-devel uuid-devel cppunit-devel protobuf-python libmicrohttpd-devel libusb-devel libftdi-devel libuuid-devel openslp-devel&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
(The remaining libs already come with the OS installation)&lt;br /&gt;
&lt;br /&gt;
== Other Distributions ==&lt;br /&gt;
&lt;br /&gt;
Install using your package manager, or build everything by hand&lt;br /&gt;
&lt;br /&gt;
If you installed things by hand (rather than using your package manager), you need to run ldconfig as root to pick up the new libraries&lt;br /&gt;
&lt;br /&gt;
  sudo  ldconfig&lt;br /&gt;
&lt;br /&gt;
=Checkout or Download an Archive=&lt;br /&gt;
&lt;br /&gt;
You can either download a tarball, or pull the latest version from the git repo&lt;br /&gt;
&lt;br /&gt;
== Tarball ==&lt;br /&gt;
&lt;br /&gt;
Download the most recent tarball from http://code.google.com/p/open-lighting/downloads/list&lt;br /&gt;
Extract using&lt;br /&gt;
&lt;br /&gt;
  tar -zxf ola-0.X.Y.tar.gz&lt;br /&gt;
  cd ola-0.X.Y&lt;br /&gt;
&lt;br /&gt;
== Git ==&lt;br /&gt;
&lt;br /&gt;
If you don't have '''git''' yet, you'll need to install it with your distro's package manager. On Debian / Ubuntu run:&lt;br /&gt;
&lt;br /&gt;
  sudo apt-get install git&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Check out the git repo with the following command:&lt;br /&gt;
&lt;br /&gt;
  git clone https://code.google.com/p/open-lighting/ ola&lt;br /&gt;
  cd ola&lt;br /&gt;
&lt;br /&gt;
{{ MacOLABuild }}&lt;br /&gt;
&lt;br /&gt;
Finally run ldconfig so you can use the new libraries.&lt;br /&gt;
&lt;br /&gt;
  sudo ldconfig&lt;br /&gt;
&lt;br /&gt;
=Device drivers=&lt;br /&gt;
Note that, for some devices, it is necessary to install drivers for OLA to work with them. For example, the [[Open DMX USB]] device needs an additional kernel module that could be built using the instuctions on [[LLA_and_Q_Light_Controller_Ubuntu_Tutorial]]. For other devices, refer to the corresponding device page on this wiki.&lt;br /&gt;
&lt;br /&gt;
=Known Issues=&lt;br /&gt;
&lt;br /&gt;
If you get an error like the following:&lt;br /&gt;
&lt;br /&gt;
 /bin/sh ./libtool --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I.   -I/opt/local/var/macports/software/protobuf-cpp/2.0.3_0/opt/local/include/  -g -O2 -c -o ltdl.lo ltdl.c&lt;br /&gt;
 ./libtool: line 464: CDPATH: command not found&lt;br /&gt;
 /Users/simonn/lighting/lla/libltdl/libtool: line 464: CDPATH: command not found&lt;br /&gt;
 /Users/simonn/lighting/lla/libltdl/libtool: line 1142: func_opt_split: command not found&lt;br /&gt;
 libtool: Version mismatch error.  This is libtool 2.2.6, but the&lt;br /&gt;
 libtool: definition of this LT_INIT comes from an older release.&lt;br /&gt;
 libtool: You should recreate aclocal.m4 with macros from libtool 2.2.6&lt;br /&gt;
 libtool: and run autoconf again.&lt;br /&gt;
&lt;br /&gt;
Your system uses a different version of libtool. Run:&lt;br /&gt;
&lt;br /&gt;
  libtoolize --ltdl -c -f&lt;br /&gt;
&lt;br /&gt;
and then start from the autoreconf step again.&lt;br /&gt;
&lt;br /&gt;
If you should get the following error try to fix it with one of [http://groups.google.com/group/open-lighting/msg/72060f6327d30df6 two available solutions]:&lt;br /&gt;
&lt;br /&gt;
 Rpc.pb.cc: In copy constructor 'ola::rpc::RpcMessage::RpcMessage(const ola::rpc::RpcMessage&amp;amp;)': &lt;br /&gt;
 Rpc.pb.cc:143: error: base class 'class google::protobuf::Message' should be explicitly initialized in the copy constructor &lt;br /&gt;
&lt;br /&gt;
You should be able to prevent this by [http://groups.google.com/group/open-lighting/msg/c6d86d03dd74ed5b editing &amp;lt;code&amp;gt;./src/Makefile.am&amp;lt;/code&amp;gt;], removing &amp;lt;code&amp;gt;-Werror&amp;lt;/code&amp;gt; and then start from the autoreconfig step again.&lt;/div&gt;</summary>
		<author><name>Nightrune</name></author>	</entry>

	</feed>