wiki.openlighting.org - User contributions [en]

Raspberry Pi Media Player

2013-12-29T00:10:14Z

Mrpackethead: Created page with "Being stuck at home definatly has its advantages, one is that i finally got to mess with my Raspberry PI's a little.. What i've wanted for quite a while is to be able to trigg..."

Being stuck at home definatly has its advantages, one is that i finally got to mess with my Raspberry PI's a little.. What i've wanted for quite a while is to be able to trigger Video/audio via DMX/E1.31/Artnet.. And now i have the start of solution.

(1) Rasberry PI model B, 4GB Class 4 SDcard ( i'm using a SanDisk one )..
(2) Used Raspbian Operating System. ( Raspbian is Debian Linux built for raspberry PI ).. i'm sure you can use somethign else if you want
(3) Installed Open Lighting Architecture ( www.opendmx.net )

Media playback is via omxplayer ( its part of the raspbian build );

to play a file, its pretty simple.. You'll obviously need to copy a file to the machien or be able to access it via a network.

omxplayer file.mp4 ; there are some other options like -o hdmi to play audio via the hdmi, etc, check the man pages

omxplayer accepts some basic transport controls via keypress's... ie 'p' for pause.. Not much use for control via DMX... so..

set up a FIFO ( mkfifo /tmp/cmd )

Start up omxplayer with a redirect

omxplayer file.mp4 < /tmp/cmd it will just sit there;

then via the fifo send it some key press's

aka;

echo -n p > /tmp/cmd this sends it a pause, but what it will do is load the file to memory and be ready to play.

send it another 'p' and it will play

echo -n p >/tmp/cmd

ok, so thats not Dmx controlled.. thats where OLA_trigger comes in.

OLA trigger lets you run arbitory commands based on the values of DMX data coming in..
http://www.opendmx.net/index.php/OLA_DMX_Trigger

Unfortuantly you can't use a redirect in the OLA config file, so what i do is create a small shell script, and make the action in the OLA trigger config, that shell script..

Config file looks like this

1 128-255 mycommands

Shell script is really simple and looks like this;

echo -n p >/tmp/cmd

You also of course need to have configured teh universes in OLA.. Then from your favorite sequencer you can send it dmx commands and fire off your videos in sync.. The methods can be extended of course to be able to select multiple videos and the likes..

Still a work in progress, and certainly the above is likely to be confusing and definatly incomplete, but it actually works, and you have a HD 1080p capable palyer for $35 that you can control via dmx or e1.31

OLA ArtNet Roadmap

2013-03-08T23:55:45Z

Mrpackethead: /* Investigate Optimizing the Send Path */

This describes proposed changes to the [[OLA]] [[ArtNet]] plugin to make it more usable. Some of the use cases that have been requested include:

* Receiving broadcast ArtNet data and unicasting to a static list of destinations
* Converting many universes (10s, 100s?) from ArtNet to E1.31 and visa versa.

== Usecases ==

''
Using OLA as a 'protocol' converter, to allow equipment that is otherwise incompatible to work together.''

Artnet-1 to Artnet-2. There are some media servers that do not support Unicast Art-net at all, and all packets are broadcast. When the number of universes exceeds some threshold ( typically >20 ) many end devices can't cope with the number of packets that are needed to be discarded. You end up with irractic and laggy results. ( end devices typically have low power embedded microcontrollers ). Broacast packets need to received from a console/media server and retransmitted in unicast. Its important to be able to either use the Art-net poll mechanism to auto-populate which universes are required on which devices or to use a 'static' routing system. Because we are listening to an Art-net Speaking console, we need to be listen to a large number of universes.

A typical device that we would want to listen to could be a GrandMA VPU. It does not support Static assignment of Universes to IP address', and there is a requirement to be able to send more than 4 universes to an Art-net device..

''Using OLA as a 'protocol' converter, from Art-net to E1.31
''
Similar to above, but receiving Art-net and transmitting in E1.31.. It woudl be good to be able to support E1.31 in both Multicast and Unicast.

== Requirements ==
* Support multiple ArtNet Devices, one per logical network interface.
* Support unicasting data to a static list of IPv4 addresses.
* Support more than 4 ports in both directions
* De-couple the ArtNet universe from the OLA universe number to support any-way patching. i.e. patch ArtNet universe 5 to OLA universe 3.

== Proposed Changes==

=== Investigate Optimizing the Send Path ===

The [http://man7.org/linux/man-pages/man2/sendmmsg.2.html sendmmsg] syscall was added in Linux 3.0. It allows multiple datagrams to be sent with a single syscall. sendmmsg would allos us to reduce the number of syscalls required for each ArtNet packet when unicasting. This scope of this change is to make the required changes and then benchmark the performance.

Steps:
* Detect support for sendmmsg in configure.ac
* Add a method to the UDPSocket class to enable a single data message to be sent to many addresses
* Modify the ArtNetNode::SendDMX method to use the new UDPSocket method

''with the large number of universes being used, the likely scenario is that most universes will only be used at a single destination, the number of replicated packets probalby is quite low''

=== Multiple ArtNet Devices ===

Right now only a single ArtNet Device is created. This should be changed so that OLA creates [https://code.google.com/p/open-lighting/source/browse/plugins/artnet/ArtNetPlugin.cpp#45 one device per logical interface].

Currently the ArtNetNode object binds to the wildcard address ([https://code.google.com/p/open-lighting/source/browse/plugins/artnet/ArtNetNode.cpp#1636 code]) which means trying to create a second instance will fail.

We need some research into how broadcast traffic is handled with multiple interfaces. Ideally each instance should bind to the broadcast addresses for the specified logical interface.

=== Increased Output Ports ===

=== Increased Input Ports ===

OLA ArtNet Roadmap

2013-03-08T23:52:43Z

Mrpackethead: /* Usecases */

This describes proposed changes to the [[OLA]] [[ArtNet]] plugin to make it more usable. Some of the use cases that have been requested include:

* Receiving broadcast ArtNet data and unicasting to a static list of destinations
* Converting many universes (10s, 100s?) from ArtNet to E1.31 and visa versa.

== Usecases ==

''
Using OLA as a 'protocol' converter, to allow equipment that is otherwise incompatible to work together.''

Artnet-1 to Artnet-2. There are some media servers that do not support Unicast Art-net at all, and all packets are broadcast. When the number of universes exceeds some threshold ( typically >20 ) many end devices can't cope with the number of packets that are needed to be discarded. You end up with irractic and laggy results. ( end devices typically have low power embedded microcontrollers ). Broacast packets need to received from a console/media server and retransmitted in unicast. Its important to be able to either use the Art-net poll mechanism to auto-populate which universes are required on which devices or to use a 'static' routing system. Because we are listening to an Art-net Speaking console, we need to be listen to a large number of universes.

A typical device that we would want to listen to could be a GrandMA VPU. It does not support Static assignment of Universes to IP address', and there is a requirement to be able to send more than 4 universes to an Art-net device..

''Using OLA as a 'protocol' converter, from Art-net to E1.31
''
Similar to above, but receiving Art-net and transmitting in E1.31.. It woudl be good to be able to support E1.31 in both Multicast and Unicast.

== Requirements ==
* Support multiple ArtNet Devices, one per logical network interface.
* Support unicasting data to a static list of IPv4 addresses.
* Support more than 4 ports in both directions
* De-couple the ArtNet universe from the OLA universe number to support any-way patching. i.e. patch ArtNet universe 5 to OLA universe 3.

== Proposed Changes==

=== Investigate Optimizing the Send Path ===

The [http://man7.org/linux/man-pages/man2/sendmmsg.2.html sendmmsg] syscall was added in Linux 3.0. It allows multiple datagrams to be sent with a single syscall. sendmmsg would allos us to reduce the number of syscalls required for each ArtNet packet when unicasting. This scope of this change is to make the required changes and then benchmark the performance.

Steps:
* Detect support for sendmmsg in configure.ac
* Add a method to the UDPSocket class to enable a single data message to be sent to many addresses
* Modify the ArtNetNode::SendDMX method to use the new UDPSocket method

=== Multiple ArtNet Devices ===

Right now only a single ArtNet Device is created. This should be changed so that OLA creates [https://code.google.com/p/open-lighting/source/browse/plugins/artnet/ArtNetPlugin.cpp#45 one device per logical interface].

Currently the ArtNetNode object binds to the wildcard address ([https://code.google.com/p/open-lighting/source/browse/plugins/artnet/ArtNetNode.cpp#1636 code]) which means trying to create a second instance will fail.

We need some research into how broadcast traffic is handled with multiple interfaces. Ideally each instance should bind to the broadcast addresses for the specified logical interface.

=== Increased Output Ports ===

=== Increased Input Ports ===

OLA ArtNet Roadmap

2013-03-08T23:43:05Z

Mrpackethead: /* Usecases ==== Usecases */

This describes proposed changes to the [[OLA]] [[ArtNet]] plugin to make it more usable. Some of the use cases that have been requested include:

* Receiving broadcast ArtNet data and unicasting to a static list of destinations
* Converting many universes (10s, 100s?) from ArtNet to E1.31 and visa versa.

== Usecases ==

Using OLA as a 'protocol' converter, to allow equipment that is otherwise incompatible to work together.

Artnet-1 to Artnet-2. There are some media servers that do not support Unicast Art-net at all, and all packets are broadcast. When the number of universes exceeds some threshold ( typically >20 ) many end devices can't cope with the number of packets that are needed to be discarded. You end up with irractic and laggy results. ( end devices typically have low power embedded microcontrollers ). Broacast packets need to received from a console/media server and retransmitted in unicast. Its important to be able to either use the Art-net poll mechanism to auto-populate which universes are required on which devices or to use a 'static' routing system. Because we are listening to an Art-net Speaking console, we need to be listen to a large number of universes.

A typical device that we would want to listen to could be a GrandMA VPU. It does not support Static assignment of Universes to IP address', and there is a requirement to be able to send more than 4 universes to an Art-net device..

Using OLA as a 'protocol' converter, from Art-net to E1.31

Similar to above, but receiving Art-net and transmitting in E1.31.. It woudl be good to be able to support E1.31 in both Multicast and Unicast.

== Requirements ==
* Support multiple ArtNet Devices, one per logical network interface.
* Support unicasting data to a static list of IPv4 addresses.
* Support more than 4 ports in both directions
* De-couple the ArtNet universe from the OLA universe number to support any-way patching. i.e. patch ArtNet universe 5 to OLA universe 3.

== Proposed Changes==

=== Investigate Optimizing the Send Path ===

The [http://man7.org/linux/man-pages/man2/sendmmsg.2.html sendmmsg] syscall was added in Linux 3.0. It allows multiple datagrams to be sent with a single syscall. sendmmsg would allos us to reduce the number of syscalls required for each ArtNet packet when unicasting. This scope of this change is to make the required changes and then benchmark the performance.

Steps:
* Detect support for sendmmsg in configure.ac
* Add a method to the UDPSocket class to enable a single data message to be sent to many addresses
* Modify the ArtNetNode::SendDMX method to use the new UDPSocket method

=== Multiple ArtNet Devices ===

Right now only a single ArtNet Device is created. This should be changed so that OLA creates [https://code.google.com/p/open-lighting/source/browse/plugins/artnet/ArtNetPlugin.cpp#45 one device per logical interface].

Currently the ArtNetNode object binds to the wildcard address ([https://code.google.com/p/open-lighting/source/browse/plugins/artnet/ArtNetNode.cpp#1636 code]) which means trying to create a second instance will fail.

We need some research into how broadcast traffic is handled with multiple interfaces. Ideally each instance should bind to the broadcast addresses for the specified logical interface.

=== Increased Output Ports ===

=== Increased Input Ports ===

OLA ArtNet Roadmap

2013-03-08T23:42:36Z

Mrpackethead: /* Usecases */

This describes proposed changes to the [[OLA]] [[ArtNet]] plugin to make it more usable. Some of the use cases that have been requested include:

* Receiving broadcast ArtNet data and unicasting to a static list of destinations
* Converting many universes (10s, 100s?) from ArtNet to E1.31 and visa versa.

== Usecases ==== Usecases ==

Using OLA as a 'protocol' converter, to allow equipment that is otherwise incompatible to work together.

Artnet-1 to Artnet-2. There are some media servers that do not support Unicast Art-net at all, and all packets are broadcast. When the number of universes exceeds some threshold ( typically >20 ) many end devices can't cope with the number of packets that are needed to be discarded. You end up with irractic and laggy results. ( end devices typically have low power embedded microcontrollers ). Broacast packets need to received from a console/media server and retransmitted in unicast. Its important to be able to either use the Art-net poll mechanism to auto-populate which universes are required on which devices or to use a 'static' routing system. Because we are listening to an Art-net Speaking console, we need to be listen to a large number of universes.

A typical device that we would want to listen to could be a GrandMA VPU. It does not support Static assignment of Universes to IP address', and there is a requirement to be able to send more than 4 universes to an Art-net device..

Using OLA as a 'protocol' converter, from Art-net to E1.31

Similar to above, but receiving Art-net and transmitting in E1.31.. It woudl be good to be able to support E1.31 in both Multicast and Unicast.

== Requirements ==
* Support multiple ArtNet Devices, one per logical network interface.
* Support unicasting data to a static list of IPv4 addresses.
* Support more than 4 ports in both directions
* De-couple the ArtNet universe from the OLA universe number to support any-way patching. i.e. patch ArtNet universe 5 to OLA universe 3.

== Proposed Changes==

=== Investigate Optimizing the Send Path ===

The [http://man7.org/linux/man-pages/man2/sendmmsg.2.html sendmmsg] syscall was added in Linux 3.0. It allows multiple datagrams to be sent with a single syscall. sendmmsg would allos us to reduce the number of syscalls required for each ArtNet packet when unicasting. This scope of this change is to make the required changes and then benchmark the performance.

Steps:
* Detect support for sendmmsg in configure.ac
* Add a method to the UDPSocket class to enable a single data message to be sent to many addresses
* Modify the ArtNetNode::SendDMX method to use the new UDPSocket method

=== Multiple ArtNet Devices ===

Right now only a single ArtNet Device is created. This should be changed so that OLA creates [https://code.google.com/p/open-lighting/source/browse/plugins/artnet/ArtNetPlugin.cpp#45 one device per logical interface].

Currently the ArtNetNode object binds to the wildcard address ([https://code.google.com/p/open-lighting/source/browse/plugins/artnet/ArtNetNode.cpp#1636 code]) which means trying to create a second instance will fail.

We need some research into how broadcast traffic is handled with multiple interfaces. Ideally each instance should bind to the broadcast addresses for the specified logical interface.

=== Increased Output Ports ===

=== Increased Input Ports ===

OLA ArtNet Roadmap

2013-03-08T23:01:49Z

Mrpackethead:

Open Lighting Project

2013-02-04T22:11:58Z

Mrpackethead:

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.

<table style="width: 100%; margin:4px 0 0 0; background:none; border-spacing: 5px;">
<tr>
<td style="width:45%; border:1px solid #cedff2; background:#f5faff; vertical-align:top; padding: 4px">
[[Image:OLA-Logo-Fitted-48px.png|right|link=OLA]]
<h2 style="float:left; font-size:120%; padding: .2em; margin:3px; font-weight:bold;">The Open Lighting Architecture</h2>
<div style="clear: left">
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.
</div>
</td>
<td style="width:45%; border:1px solid #cedff2; background:#f5faff; vertical-align:top; padding: 4px">
[[Image:rdm-logo-small.png|right|link=]]
<h2 style="float:left; font-size:120%; padding: .2em; margin:3px; font-weight:bold;">RDM Responder Tests</h2>
<div style="clear: left">
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.

For questions about the RDM Responder tests, email the [http://groups.google.com/group/rdm-testing RDM Testing List].
</div>
</td>
</tr>
<tr><td colspan="2"> </td></tr>
<tr>
<td style="width:45%; border:1px solid #cedff2; background:#f5faff; vertical-align:top; padding: 4px">
[[Image:raspi-logo-small.png|right|link=]]
<h2 style="float:left; font-size:120%; padding: .2em; margin:3px; font-weight:bold;">OLA on the Raspberry Pi</h2>
<div style="clear: left">
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.
</div>
</td>

<td style="width:45%; border:1px solid #cedff2; background:#f5faff; vertical-align:top; padding: 4px">
[[Image:Robin-1200.png|right|link=]]
<h2 style="float:left; font-size:120%; padding: .2em; margin:3px; font-weight:bold;">rdm.openlighting.org</h2>
<div style="clear: left">
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.
</div>
</td>
</tr>

<tr><td colspan="2"> </td></tr>
<tr>
<td style="width:45%; border:1px solid #cedff2; background:#f5faff; vertical-align:top; padding: 4px">
[[Image:Email-icon.png|right|link=]]
<h2 style="float:left; font-size:120%; padding: .2em; margin:3px; font-weight:bold;">Contact / Support</h2>
<div style="clear: left">
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:

* Primary User & Developer Discussion [http://groups.google.com/group/open-lighting Open Lighting Discuss] (typically a few messages per day).
* Announcements are posted to [http://groups.google.com/group/open-lighting-announce Open Lighting Announce] (low volume, typically 1-2 per month)
* RDM Testing Discussion [http://groups.google.com/group/rdm-testing RDM Testing].
* IRC #openlighting on freenode.net
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.
</div>
</td>

<td style="width:45%; border:1px solid #cedff2; background:#f5faff; vertical-align:top; padding: 4px">
<h2 style="float:left; font-size:120%; padding: .2em; margin:3px; font-weight:bold;">Other Projects</h2>
<div style="clear: left">
* [[libartnet]]. The library that started it all, libartnet is an [[ArtNet]] implementation for Mac, Linux and Windows & iPhone.
* [[Arduino RGB Mixer]], open source firmware for Arduinos, so that they can be used as a simple RGB Color Mixer. Now with RDM support!
* [[OLA_DMX_Trigger | DMX Trigger]], this can execute command line programs based on DMX values. It's useful for building DMX controlled media players.
</div>
</td>
</tr>

<tr><td colspan="2"> </td></tr>
<tr>
<td style="width:45%; border:1px solid #cedff2; background:#f5faff; vertical-align:top; padding: 4px">
<h2 style="float:left; font-size:120%; padding: .2em; margin:3px; font-weight:bold;">Project Supporters</h2>
<div style="clear: left">
Many individuals & organizations have supported the project over the years. We're grateful to all of them.

* [http://www.anyma.ch Anyma], provided a [[Anyma_uDMX|uDMX]]
* [[Artistic Licence]], provided a [[Net-Lynx]] & Down-Lynx for Art-Net / RDM testing and a [[Rail-Tran]] to test [[RDM]] support
* Andrew Frazer, who sponsored the development of ola_trigger with a [[RDM USB Pro]]
* [http://www.creativelighting.com.au/ Creative Lighting], provided a [[SLAMMO XC-1]] & [[ADDICT]] for [[RDM]] testing.
* [[Enttec]], provided a [[DMX USB Pro]]
* Eric Johnson, for hosting the server used to test & debug much of the RDM code.
* Florian from eventa.ag who donated a [[StageProfi]] and a [[USBDMX2]]
* [http://www.goddarddesign.com/ Goddard Design], who made available a [[MiniDMXter]]
* Jason Kyle from [http://www.DMXking.com DMXKing.com] provided a [[DMXking USB DMX512-A]]
* [[JESE]], provided a [[DMX-TRI]] & [[RDM-TRI]] & Tempest Enclosure to test the RDM implementation.
* [http://www.ljusdesign.se LjusDesign AB] who donated 7 RDM splitters.
* [http://www.lumenradio.com/ LumenRadio] who provided a Nova TX2 RDM, Nova RX RDM and Nova FX units and a Raspberry Pi.
* [http://www.martin.com Martin Professional A/S] which loaned a Mac 700 for RDM testing
* [http://www.milinst.co.uk/ Milford Instruments] who sent 3 RDMChips for testing.
* Peter Kirkup, from [http://www.zero88.com/ Zero 88] who donated a Betapack 3
* Petr from [[ROBE Lighting]] who loaned a [[Robe Universal Interface]] and [http://www.robe.cz/products/article/robin-600e-spot/ Robin 600]
* [http://www.sandsys.com/ Sandsys], donated a [http://www.sandsys.com/products/SB-AAA2100.htm SandBox]
* Shaun Jackman, answered questions about the [[:Category:Pathport|Pathport]] Protocol
* [http://soundlight.de/ SoundLight] who loaned a 3604PWM-H device
* [http://www.waapa.ecu.edu.au West Australian Academy of Performing Arts] (WAAPA) for access to a [[Strand Lighting]] console.

</div>
</td>

<td style="width:45%; border:1px solid #cedff2; background:#f5faff; vertical-align:top; padding: 4px">
<h2 style="float:left; font-size:120%; padding: .2em; margin:3px; font-weight:bold;">Get Involved</h2>
<div style="clear: left">
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]

* Technical Writers, the documentation could do with some cleanup.
* Packagers, we need people to build binary packages for Mac, Debian/Ubuntu and RPM-based distros
* Windows programmers, are you interested in helping [[Building_OLA_for_Windows| port OLA to Windows]]?
* Java programmers, we need someone to write the Java client API [http://code.google.com/p/linux-lighting/issues/detail?id=15 ]
* 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.
* Web designers, the web UI could do with a facelift.

The programming team behind OLA consists of:
* Bastien Andrès, contributed to the dmx4linux plugin
* Harry F, for the Eurolite USB Pro code
* Heikki Junnila, bug fixes for the debian packaging files
* Laurent (Renzo), Debian packages, FreeBSD & RDM testing.
* Masaki Muranaka, various patches
* Nicolas, for the win32 port of libartnet
* Ravindra Nath Kakarla, RDM Test Server (Part of [http://www.google-melange.com/gsoc/profile/organization/google/gsoc2012/openlighting Google Summer of Code 2012] ).
* Rowan Maclachlan (hippy) for various changes
* Rui Barreiros for the FTDI plugin
* Tobi Schäfer, for the MacPort files
</div>
</td>
</tr>
</table>

__NOTOC__

Open Lighting Project

2013-02-04T22:11:17Z

Mrpackethead:

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.

<table style="width: 100%; margin:4px 0 0 0; background:none; border-spacing: 5px;">
<tr>
<td style="width:45%; border:1px solid #cedff2; background:#f5faff; vertical-align:top; padding: 4px">
[[Image:OLA-Logo-Fitted-48px.png|right|link=OLA]]
<h2 style="float:left; font-size:120%; padding: .2em; margin:3px; font-weight:bold;">The Open Lighting Architecture</h2>
<div style="clear: left">
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.
</div>
</td>
<td style="width:45%; border:1px solid #cedff2; background:#f5faff; vertical-align:top; padding: 4px">
[[Image:rdm-logo-small.png|right|link=]]
<h2 style="float:left; font-size:120%; padding: .2em; margin:3px; font-weight:bold;">RDM Responder Tests</h2>
<div style="clear: left">
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.

For questions about the RDM Responder tests, email the [http://groups.google.com/group/rdm-testing RDM Testing List].
</div>
</td>
</tr>
<tr><td colspan="2"> </td></tr>
<tr>
<td style="width:45%; border:1px solid #cedff2; background:#f5faff; vertical-align:top; padding: 4px">
[[Image:raspi-logo-small.png|right|link=]]
<h2 style="float:left; font-size:120%; padding: .2em; margin:3px; font-weight:bold;">OLA on the Raspberry Pi</h2>
<div style="clear: left">
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.
</div>
</td>

<td style="width:45%; border:1px solid #cedff2; background:#f5faff; vertical-align:top; padding: 4px">
[[Image:Robin-1200.png|right|link=]]
<h2 style="float:left; font-size:120%; padding: .2em; margin:3px; font-weight:bold;">rdm.openlighting.org</h2>
<div style="clear: left">
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.
</div>
</td>
</tr>

<tr><td colspan="2"> </td></tr>
<tr>
<td style="width:45%; border:1px solid #cedff2; background:#f5faff; vertical-align:top; padding: 4px">
[[Image:Email-icon.png|right|link=]]
<h2 style="float:left; font-size:120%; padding: .2em; margin:3px; font-weight:bold;">Contact / Support</h2>
<div style="clear: left">
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:

* Primary User & Developer Discussion [http://groups.google.com/group/open-lighting Open Lighting Discuss] (typically a few messages per day).
* Announcements are posted to [http://groups.google.com/group/open-lighting-announce Open Lighting Announce] (low volume, typically 1-2 per month)
* RDM Testing Discussion [http://groups.google.com/group/rdm-testing RDM Testing].
* IRC #freenode on freenode.net
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.
</div>
</td>

<td style="width:45%; border:1px solid #cedff2; background:#f5faff; vertical-align:top; padding: 4px">
<h2 style="float:left; font-size:120%; padding: .2em; margin:3px; font-weight:bold;">Other Projects</h2>
<div style="clear: left">
* [[libartnet]]. The library that started it all, libartnet is an [[ArtNet]] implementation for Mac, Linux and Windows & iPhone.
* [[Arduino RGB Mixer]], open source firmware for Arduinos, so that they can be used as a simple RGB Color Mixer. Now with RDM support!
* [[OLA_DMX_Trigger | DMX Trigger]], this can execute command line programs based on DMX values. It's useful for building DMX controlled media players.
</div>
</td>
</tr>

<tr><td colspan="2"> </td></tr>
<tr>
<td style="width:45%; border:1px solid #cedff2; background:#f5faff; vertical-align:top; padding: 4px">
<h2 style="float:left; font-size:120%; padding: .2em; margin:3px; font-weight:bold;">Project Supporters</h2>
<div style="clear: left">
Many individuals & organizations have supported the project over the years. We're grateful to all of them.

* [http://www.anyma.ch Anyma], provided a [[Anyma_uDMX|uDMX]]
* [[Artistic Licence]], provided a [[Net-Lynx]] & Down-Lynx for Art-Net / RDM testing and a [[Rail-Tran]] to test [[RDM]] support
* Andrew Frazer, who sponsored the development of ola_trigger with a [[RDM USB Pro]]
* [http://www.creativelighting.com.au/ Creative Lighting], provided a [[SLAMMO XC-1]] & [[ADDICT]] for [[RDM]] testing.
* [[Enttec]], provided a [[DMX USB Pro]]
* Eric Johnson, for hosting the server used to test & debug much of the RDM code.
* Florian from eventa.ag who donated a [[StageProfi]] and a [[USBDMX2]]
* [http://www.goddarddesign.com/ Goddard Design], who made available a [[MiniDMXter]]
* Jason Kyle from [http://www.DMXking.com DMXKing.com] provided a [[DMXking USB DMX512-A]]
* [[JESE]], provided a [[DMX-TRI]] & [[RDM-TRI]] & Tempest Enclosure to test the RDM implementation.
* [http://www.ljusdesign.se LjusDesign AB] who donated 7 RDM splitters.
* [http://www.lumenradio.com/ LumenRadio] who provided a Nova TX2 RDM, Nova RX RDM and Nova FX units and a Raspberry Pi.
* [http://www.martin.com Martin Professional A/S] which loaned a Mac 700 for RDM testing
* [http://www.milinst.co.uk/ Milford Instruments] who sent 3 RDMChips for testing.
* Peter Kirkup, from [http://www.zero88.com/ Zero 88] who donated a Betapack 3
* Petr from [[ROBE Lighting]] who loaned a [[Robe Universal Interface]] and [http://www.robe.cz/products/article/robin-600e-spot/ Robin 600]
* [http://www.sandsys.com/ Sandsys], donated a [http://www.sandsys.com/products/SB-AAA2100.htm SandBox]
* Shaun Jackman, answered questions about the [[:Category:Pathport|Pathport]] Protocol
* [http://soundlight.de/ SoundLight] who loaned a 3604PWM-H device
* [http://www.waapa.ecu.edu.au West Australian Academy of Performing Arts] (WAAPA) for access to a [[Strand Lighting]] console.

</div>
</td>

<td style="width:45%; border:1px solid #cedff2; background:#f5faff; vertical-align:top; padding: 4px">
<h2 style="float:left; font-size:120%; padding: .2em; margin:3px; font-weight:bold;">Get Involved</h2>
<div style="clear: left">
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]

* Technical Writers, the documentation could do with some cleanup.
* Packagers, we need people to build binary packages for Mac, Debian/Ubuntu and RPM-based distros
* Windows programmers, are you interested in helping [[Building_OLA_for_Windows| port OLA to Windows]]?
* Java programmers, we need someone to write the Java client API [http://code.google.com/p/linux-lighting/issues/detail?id=15 ]
* 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.
* Web designers, the web UI could do with a facelift.

The programming team behind OLA consists of:
* Bastien Andrès, contributed to the dmx4linux plugin
* Harry F, for the Eurolite USB Pro code
* Heikki Junnila, bug fixes for the debian packaging files
* Laurent (Renzo), Debian packages, FreeBSD & RDM testing.
* Masaki Muranaka, various patches
* Nicolas, for the win32 port of libartnet
* Ravindra Nath Kakarla, RDM Test Server (Part of [http://www.google-melange.com/gsoc/profile/organization/google/gsoc2012/openlighting Google Summer of Code 2012] ).
* Rowan Maclachlan (hippy) for various changes
* Rui Barreiros for the FTDI plugin
* Tobi Schäfer, for the MacPort files
</div>
</td>
</tr>
</table>

__NOTOC__

OLA on Beaglebone

2013-01-07T20:41:45Z

Mrpackethead:

This describes how to get [[OLA]] working on a Beaglebone from strach. At the time of writing, an "image" does not exist for the beagle bone. This process is based on using the debian os. There certainly are other ways of bulding this, but this is a method that works for me.

==Preparing your debian based Beaglebone==

Get Robert C nelsons Netinstall scripts,

https://github.com/RobertCNelson/netinstall

cd /netinstall
./mk_mmc.sh --uboot bone --mmc /dev/sdX ( sdX ) is the card

this will build the boot loader onto the card. This is also based on debian Squeeze.

Once its done, put the card in your beagle, and start up. You'll need to connect the Beaglebone via USB, and talk to it via Screen. Follow the instructions for the debian install.. Select SSH server and System Ultiities for your build. It can take a while to finish a build, depending on how fast your internet connections are.

=Install dependencies =

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.

First you'll need at least the following:
* cppunit
* uuid or ossp uuid
* pkg-config
* curses
* lex (or flex)
* yacc (or bison)
* the protocol buffers library [http://code.google.com/p/protobuf/ http://code.google.com/p/protobuf/] (version 2.3.0 or later)
* microhttpd [ftp://ftp.gnu.org/gnu/libmicrohttpd/ ftp://ftp.gnu.org/gnu/libmicrohttpd/] (if you want the web UI). You need version >= 0.4.0 of microhttpd

If you're building from git you'll also need the following:

* libtool
* automake
* autoconf

sudo apt-get install libcppunit-dev libcppunit-1.12-1 uuid-dev pkg-config libncurses5-dev libtool autoconf automake g++ libmicrohttpd-dev libmicrohttpd5 protobuf-c-compiler libprotobuf-lite6 python-protobuf libprotobuf-dev zlib1g-dev bison flex make libftdi-dev libftdi1 libusb-1.0-0-dev liblo-dev git

Note, these dependancys are slightly different from the Debian build

== Install OLA ==

Check out the git repo with the following command:

cd /usr/local/src ( not entirely nessary, but you will be able to find it later )
git clone https://code.google.com/p/open-lighting/ ola
cd ola

Run autoreconf

autoreconf -i

./configure --enable-rdm-tests --enable-python-libs
make
make check
sudo make install

Finally run ldconfig so you can use the new libraries.
sudo ldconfig

OLA on Beaglebone

2013-01-07T20:26:51Z

Mrpackethead: /* Install OLA */

This describes how to get [[OLA]] working on a Beaglebone from strach. At the time of writing, an "image" does not exist for the beagle bone. This process is based on using the debian os. There certainly are other ways of bulding this, but this is a method that works for me.

==Preparing your debian based Beaglebone==

Get Robert C nelsons Netinstall scripts,

https://github.com/RobertCNelson/netinstall

cd /netinstall
./mk_mmc.sh --uboot bone --mmc /dev/sdX ( sdX ) is the card

this will build the boot loader onto the card. This is also based on debian Squeeze.

Once its done, put the card in your beagle, and start up. You'll need to connect the Beaglebone via USB, and talk to it via Screen. Follow the instructions for the debian install.. Select SSH server and System Ultiities for your build. It can take a while to finish a build, depending on how fast your internet connections are.

=Install dependencies =

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.

First you'll need at least the following:
* cppunit
* uuid or ossp uuid
* pkg-config
* curses
* lex (or flex)
* yacc (or bison)
* the protocol buffers library [http://code.google.com/p/protobuf/ http://code.google.com/p/protobuf/] (version 2.3.0 or later)
* microhttpd [ftp://ftp.gnu.org/gnu/libmicrohttpd/ ftp://ftp.gnu.org/gnu/libmicrohttpd/] (if you want the web UI). You need version >= 0.4.0 of microhttpd

If you're building from git you'll also need the following:

* libtool
* automake
* autoconf

sudo apt-get install libcppunit-dev libcppunit-1.12-1 uuid-dev pkg-config libncurses5-dev libtool autoconf automake g++ libmicrohttpd-dev libmicrohttpd5 protobuf-c-compiler libprotobuf-lite6 python-protobuf libprotobuf-dev zlib1g-dev bison flex make libftdi-dev libftdi1 libusb-1.0-0-dev liblo-dev git

Note, these dependancys are slightly different from the Debian build

== Install OLA ==

Check out the git repo with the following command:

cd /usr/local/src ( not entirely nessary, but you will be able to find it later )
git clone https://code.google.com/p/open-lighting/ ola
cd ola

Run autoreconf

autoreconf -i

./configure --enable-rdm-tests --enable-python-libs
make
make check
sudo make install

OLA on Beaglebone

2013-01-07T20:13:06Z

Mrpackethead:

This describes how to get [[OLA]] working on a Beaglebone from strach. At the time of writing, an "image" does not exist for the beagle bone. This process is based on using the debian os. There certainly are other ways of bulding this, but this is a method that works for me.

==Preparing your debian based Beaglebone==

Get Robert C nelsons Netinstall scripts,

https://github.com/RobertCNelson/netinstall

cd /netinstall
./mk_mmc.sh --uboot bone --mmc /dev/sdX ( sdX ) is the card

this will build the boot loader onto the card. This is also based on debian Squeeze.

Once its done, put the card in your beagle, and start up. You'll need to connect the Beaglebone via USB, and talk to it via Screen. Follow the instructions for the debian install.. Select SSH server and System Ultiities for your build. It can take a while to finish a build, depending on how fast your internet connections are.

=Install dependencies =

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.

First you'll need at least the following:
* cppunit
* uuid or ossp uuid
* pkg-config
* curses
* lex (or flex)
* yacc (or bison)
* the protocol buffers library [http://code.google.com/p/protobuf/ http://code.google.com/p/protobuf/] (version 2.3.0 or later)
* microhttpd [ftp://ftp.gnu.org/gnu/libmicrohttpd/ ftp://ftp.gnu.org/gnu/libmicrohttpd/] (if you want the web UI). You need version >= 0.4.0 of microhttpd

If you're building from git you'll also need the following:

* libtool
* automake
* autoconf

sudo apt-get install libcppunit-dev libcppunit-1.12-1 uuid-dev pkg-config libncurses5-dev libtool autoconf automake g++ libmicrohttpd-dev libmicrohttpd5 protobuf-c-compiler libprotobuf-lite6 python-protobuf libprotobuf-dev zlib1g-dev bison flex make libftdi-dev libftdi1 libusb-1.0-0-dev liblo-dev git

Note, these dependancys are slightly different from the Debian build

== Install OLA ==

Check out the git repo with the following command:

cd /usr/local/src ( not entirely nessary, but you will be able to find it later )
git clone https://code.google.com/p/open-lighting/ ola
cd ola

OLA on Beaglebone

2013-01-07T20:00:08Z

Mrpackethead:

This describes how to get [[OLA]] working on a Beaglebone from strach. At the time of writing, an "image" does not exist for the beagle bone. This process is based on using the debian os. There certainly are other ways of bulding this, but this is a method that works for me.

==Preparing your debian based Beaglebone==

Get Robert C nelsons Netinstall scripts,

https://github.com/RobertCNelson/netinstall

cd /netinstall
./mk_mmc.sh --uboot bone --mmc /dev/sdX ( sdX ) is the card

this will build the boot loader onto the card. This is also based on debian Squeeze.

Once its done, put the card in your beagle, and start up. You'll need to connect the Beaglebone via USB, and talk to it via Screen. Follow the instructions for the debian install.. Select SSH server and System Ultiities for your build. It can take a while to finish a build, depending on how fast your internet connections are.

=Install dependencies =

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.

First you'll need at least the following:
* cppunit
* uuid or ossp uuid
* pkg-config
* curses
* lex (or flex)
* yacc (or bison)
* the protocol buffers library [http://code.google.com/p/protobuf/ http://code.google.com/p/protobuf/] (version 2.3.0 or later)
* microhttpd [ftp://ftp.gnu.org/gnu/libmicrohttpd/ ftp://ftp.gnu.org/gnu/libmicrohttpd/] (if you want the web UI). You need version >= 0.4.0 of microhttpd

If you're building from git you'll also need the following:

* libtool
* automake
* autoconf

sudo apt-get install libcppunit-dev libcppunit-1.12-1 uuid-dev pkg-config libncurses5-dev libtool autoconf automake g++ libmicrohttpd-dev libmicrohttpd5 protobuf-c-compiler libprotobuf-lite6 python-protobuf libprotobuf-dev zlib1g-dev bison flex make libftdi-dev libftdi1 libusb-1.0-0-dev liblo-dev git

Note, these dependancys are slightly different from the Debian build

== Tarball ==

Download the most recent tarball from http://code.google.com/p/open-lighting/downloads/list
Extract using

tar -zxf ola-0.X.Y.tar.gz
cd ola-0.X.Y

== Git ==

If you don't have '''git''' yet, you'll need to install it with your distro's package manager. On Debian / Ubuntu run:

sudo apt-get install git

Check out the git repo with the following command:

git clone https://code.google.com/p/open-lighting/ ola
cd ola

{{ MacOLABuild }}

Finally run ldconfig so you can use the new libraries.

sudo ldconfig

=Device drivers=
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.

=Known Issues=

OLA on Beaglebone

2013-01-07T19:54:50Z

Mrpackethead: /* Preparing your debian based Beaglebone */

This describes how to get [[OLA]] working on a Beaglebone from strach. At the time of writing, an "image" does not exist for the beagle bone. This process is based on using the debian os.

==Preparing your debian based Beaglebone==

Get Robert C nelsons Netinstall scripts,

https://github.com/RobertCNelson/netinstall

cd /netinstall
./mk_mmc.sh --uboot bone --mmc /dev/sdX ( sdX ) is the card

this will build the boot loader onto the card.

=Install dependencies =

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.

First you'll need at least the following:
* cppunit
* uuid or ossp uuid
* pkg-config
* curses
* lex (or flex)
* yacc (or bison)
* the protocol buffers library [http://code.google.com/p/protobuf/ http://code.google.com/p/protobuf/] (version 2.3.0 or later)
* microhttpd [ftp://ftp.gnu.org/gnu/libmicrohttpd/ ftp://ftp.gnu.org/gnu/libmicrohttpd/] (if you want the web UI). You need version >= 0.4.0 of microhttpd

If you're building from git you'll also need the following:

* libtool
* automake
* autoconf

sudo apt-get install libcppunit-dev libcppunit-1.12-1 uuid-dev pkg-config libncurses5-dev libtool autoconf automake g++ libmicrohttpd-dev libmicrohttpd5 protobuf-c-compiler libprotobuf-lite6 python-protobuf libprotobuf-dev zlib1g-dev bison flex make libftdi-dev libftdi1 libusb-1.0-0-dev liblo-dev

Note, these dependancys are slightly different from the Debian build

== Tarball ==

Download the most recent tarball from http://code.google.com/p/open-lighting/downloads/list
Extract using

tar -zxf ola-0.X.Y.tar.gz
cd ola-0.X.Y

== Git ==

If you don't have '''git''' yet, you'll need to install it with your distro's package manager. On Debian / Ubuntu run:

sudo apt-get install git

Check out the git repo with the following command:

git clone https://code.google.com/p/open-lighting/ ola
cd ola

{{ MacOLABuild }}

Finally run ldconfig so you can use the new libraries.

sudo ldconfig

=Device drivers=
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.

=Known Issues=

OLA on Beaglebone

2013-01-07T19:45:22Z

Mrpackethead:

OLA on Beaglebone

2013-01-07T19:44:09Z

Mrpackethead: /* Debian / Ubuntu */

This describes how to get [[OLA]] working on a Beaglebone from strach. At the time of writing, an "image" does not exist for the beagle bone. This process is based on using the debian os.

==Preparing your debian based Beaglebone==

=Install dependencies =

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.

First you'll need at least the following:
* cppunit
* uuid or ossp uuid
* pkg-config
* curses
* lex (or flex)
* yacc (or bison)
* the protocol buffers library [http://code.google.com/p/protobuf/ http://code.google.com/p/protobuf/] (version 2.3.0 or later)
* microhttpd [ftp://ftp.gnu.org/gnu/libmicrohttpd/ ftp://ftp.gnu.org/gnu/libmicrohttpd/] (if you want the web UI). You need version >= 0.4.0 of microhttpd

If you're building from git you'll also need the following:

* libtool
* automake
* autoconf

sudo apt-get install libcppunit-dev libcppunit-1.12-1 uuid-dev pkg-config libncurses5-dev libtool autoconf automake g++ libmicrohttpd-dev libmicrohttpd5 protobuf-c-compiler libprotobuf-lite6 python-protobuf libprotobuf-dev zlib1g-dev bison flex make libftdi-dev libftdi1 libusb-1.0-0-dev liblo-dev

Note, these dependancys are slightly different from the Debian build

== Centos 6 / RHEL 6 / Fedora 17 ==

Users of rpm based distributions can install them with yum (protobuf*, libmicrohttpd* and libftdi* are in the EPEL repository):

sudo yum install flex bison protobuf protobuf-devel uuid-devel cppunit-devel protobuf-python libmicrohttpd-devel libusb-devel libftdi-devel libuuid-devel openslp-devel

(The remaining libs already come with the OS installation)

== Other Distributions ==

Install using your package manager, or build everything by hand

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

sudo ldconfig

=Checkout or Download an Archive=

You can either download a tarball, or pull the latest version from the git repo

== Tarball ==

Download the most recent tarball from http://code.google.com/p/open-lighting/downloads/list
Extract using

tar -zxf ola-0.X.Y.tar.gz
cd ola-0.X.Y

== Git ==

If you don't have '''git''' yet, you'll need to install it with your distro's package manager. On Debian / Ubuntu run:

sudo apt-get install git

Check out the git repo with the following command:

git clone https://code.google.com/p/open-lighting/ ola
cd ola

{{ MacOLABuild }}

Finally run ldconfig so you can use the new libraries.

sudo ldconfig

=Device drivers=
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.

=Known Issues=

If you get an error like the following:

/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
./libtool: line 464: CDPATH: command not found
/Users/simonn/lighting/lla/libltdl/libtool: line 464: CDPATH: command not found
/Users/simonn/lighting/lla/libltdl/libtool: line 1142: func_opt_split: command not found
libtool: Version mismatch error. This is libtool 2.2.6, but the
libtool: definition of this LT_INIT comes from an older release.
libtool: You should recreate aclocal.m4 with macros from libtool 2.2.6
libtool: and run autoconf again.

Your system uses a different version of libtool. Run:

libtoolize --ltdl -c -f

and then start from the autoreconf step again.

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]:

Rpc.pb.cc: In copy constructor 'ola::rpc::RpcMessage::RpcMessage(const ola::rpc::RpcMessage&)':
Rpc.pb.cc:143: error: base class 'class google::protobuf::Message' should be explicitly initialized in the copy constructor

You should be able to prevent this by [http://groups.google.com/group/open-lighting/msg/c6d86d03dd74ed5b editing <code>./src/Makefile.am</code>], removing <code>-Werror</code> and then start from the autoreconfig step again.

OLA on Beaglebone

2013-01-07T19:43:10Z

Mrpackethead: /* Debian / Ubuntu */

This describes how to get [[OLA]] working on a Beaglebone from strach. At the time of writing, an "image" does not exist for the beagle bone. This process is based on using the debian os.

==Preparing your debian based Beaglebone==

=Install dependencies =

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.

First you'll need at least the following:
* cppunit
* uuid or ossp uuid
* pkg-config
* curses
* lex (or flex)
* yacc (or bison)
* the protocol buffers library [http://code.google.com/p/protobuf/ http://code.google.com/p/protobuf/] (version 2.3.0 or later)
* microhttpd [ftp://ftp.gnu.org/gnu/libmicrohttpd/ ftp://ftp.gnu.org/gnu/libmicrohttpd/] (if you want the web UI). You need version >= 0.4.0 of microhttpd

If you're building from git you'll also need the following:

* libtool
* automake
* autoconf

== Debian / Ubuntu ==

Debian/Ubuntu users can install them with apt:

sudo apt-get install libcppunit-dev libcppunit-1.12-1 uuid-dev pkg-config libncurses5-dev libtool autoconf automake g++ libmicrohttpd-dev libmicrohttpd5 protobuf-c-compiler libprotobuf-lite6 python-protobuf libprotobuf-dev zlib1g-dev bison flex make libftdi-dev libftdi1 libusb-1.0-0-dev liblo-dev

Note: Some distributions may offer libprotobuf-lite6 instead of libprotobuf-lite7, which is an acceptable substitution.

If you're using Ubuntu 11.04 or later you can just use the command above. The versions of libprotobuf in earlier versions of Ubuntu are too old, so you'll need to install them by hand.

== Centos 6 / RHEL 6 / Fedora 17 ==

Users of rpm based distributions can install them with yum (protobuf*, libmicrohttpd* and libftdi* are in the EPEL repository):

sudo yum install flex bison protobuf protobuf-devel uuid-devel cppunit-devel protobuf-python libmicrohttpd-devel libusb-devel libftdi-devel libuuid-devel openslp-devel

(The remaining libs already come with the OS installation)

== Other Distributions ==

Install using your package manager, or build everything by hand

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

sudo ldconfig

=Checkout or Download an Archive=

You can either download a tarball, or pull the latest version from the git repo

== Tarball ==

Download the most recent tarball from http://code.google.com/p/open-lighting/downloads/list
Extract using

tar -zxf ola-0.X.Y.tar.gz
cd ola-0.X.Y

== Git ==

If you don't have '''git''' yet, you'll need to install it with your distro's package manager. On Debian / Ubuntu run:

sudo apt-get install git

Check out the git repo with the following command:

git clone https://code.google.com/p/open-lighting/ ola
cd ola

{{ MacOLABuild }}

Finally run ldconfig so you can use the new libraries.

sudo ldconfig

=Device drivers=
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.

=Known Issues=

If you get an error like the following:

/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
./libtool: line 464: CDPATH: command not found
/Users/simonn/lighting/lla/libltdl/libtool: line 464: CDPATH: command not found
/Users/simonn/lighting/lla/libltdl/libtool: line 1142: func_opt_split: command not found
libtool: Version mismatch error. This is libtool 2.2.6, but the
libtool: definition of this LT_INIT comes from an older release.
libtool: You should recreate aclocal.m4 with macros from libtool 2.2.6
libtool: and run autoconf again.

Your system uses a different version of libtool. Run:

libtoolize --ltdl -c -f

and then start from the autoreconf step again.

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]:

Rpc.pb.cc: In copy constructor 'ola::rpc::RpcMessage::RpcMessage(const ola::rpc::RpcMessage&)':
Rpc.pb.cc:143: error: base class 'class google::protobuf::Message' should be explicitly initialized in the copy constructor

You should be able to prevent this by [http://groups.google.com/group/open-lighting/msg/c6d86d03dd74ed5b editing <code>./src/Makefile.am</code>], removing <code>-Werror</code> and then start from the autoreconfig step again.

OLA on Beaglebone

2012-12-27T04:48:25Z

Mrpackethead: Created page with "This describes how to get OLA working on a Beaglebone from strach. At the time of writing, an "image" does not exist for the beagle bone. This process is based on using th…"

This describes how to get [[OLA]] working on a Beaglebone from strach. At the time of writing, an "image" does not exist for the beagle bone. This process is based on using the debian os.

==Preparing your debian based Beaglebone==

=Install dependencies =

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.

First you'll need at least the following:
* cppunit
* uuid or ossp uuid
* pkg-config
* curses
* lex (or flex)
* yacc (or bison)
* the protocol buffers library [http://code.google.com/p/protobuf/ http://code.google.com/p/protobuf/] (version 2.3.0 or later)
* microhttpd [ftp://ftp.gnu.org/gnu/libmicrohttpd/ ftp://ftp.gnu.org/gnu/libmicrohttpd/] (if you want the web UI). You need version >= 0.4.0 of microhttpd

If you're building from git you'll also need the following:

* libtool
* automake
* autoconf

== Debian / Ubuntu ==

Debian/Ubuntu users can install them with apt:

sudo apt-get install libcppunit-dev libcppunit-1.12-1 uuid-dev pkg-config libncurses5-dev libtool autoconf automake g++ libmicrohttpd-dev libmicrohttpd10 protobuf-c-compiler libprotobuf-lite7 python-protobuf libprotobuf-dev zlib1g-dev bison flex make libftdi-dev libftdi1 libusb-1.0-0-dev liblo-dev

Note: Some distributions may offer libprotobuf-lite6 instead of libprotobuf-lite7, which is an acceptable substitution.

If you're using Ubuntu 11.04 or later you can just use the command above. The versions of libprotobuf in earlier versions of Ubuntu are too old, so you'll need to install them by hand.

== Centos 6 / RHEL 6 / Fedora 17 ==

Users of rpm based distributions can install them with yum (protobuf*, libmicrohttpd* and libftdi* are in the EPEL repository):

sudo yum install flex bison protobuf protobuf-devel uuid-devel cppunit-devel protobuf-python libmicrohttpd-devel libusb-devel libftdi-devel libuuid-devel openslp-devel

(The remaining libs already come with the OS installation)

== Other Distributions ==

Install using your package manager, or build everything by hand

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

sudo ldconfig

=Checkout or Download an Archive=

You can either download a tarball, or pull the latest version from the git repo

== Tarball ==

Download the most recent tarball from http://code.google.com/p/open-lighting/downloads/list
Extract using

tar -zxf ola-0.X.Y.tar.gz
cd ola-0.X.Y

== Git ==

If you don't have '''git''' yet, you'll need to install it with your distro's package manager. On Debian / Ubuntu run:

sudo apt-get install git

Check out the git repo with the following command:

git clone https://code.google.com/p/open-lighting/ ola
cd ola

{{ MacOLABuild }}

Finally run ldconfig so you can use the new libraries.

sudo ldconfig

=Device drivers=
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.

=Known Issues=

If you get an error like the following:

/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
./libtool: line 464: CDPATH: command not found
/Users/simonn/lighting/lla/libltdl/libtool: line 464: CDPATH: command not found
/Users/simonn/lighting/lla/libltdl/libtool: line 1142: func_opt_split: command not found
libtool: Version mismatch error. This is libtool 2.2.6, but the
libtool: definition of this LT_INIT comes from an older release.
libtool: You should recreate aclocal.m4 with macros from libtool 2.2.6
libtool: and run autoconf again.

Your system uses a different version of libtool. Run:

libtoolize --ltdl -c -f

and then start from the autoreconf step again.

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]:

Rpc.pb.cc: In copy constructor 'ola::rpc::RpcMessage::RpcMessage(const ola::rpc::RpcMessage&)':
Rpc.pb.cc:143: error: base class 'class google::protobuf::Message' should be explicitly initialized in the copy constructor

You should be able to prevent this by [http://groups.google.com/group/open-lighting/msg/c6d86d03dd74ed5b editing <code>./src/Makefile.am</code>], removing <code>-Werror</code> and then start from the autoreconfig step again.

Open Lighting Architecture

2012-12-27T04:32:58Z

Mrpackethead: /* Getting Started */

[[Image:OLA-Logo-Fitted-48px.png|right]]
Link: http://code.google.com/p/open-lighting/ <br>
{{Features|free=yes|tx=yes|rx=yes|linux=yes|osx=yes|http=yes|rdm=yes}}
[[Image:Ola-download.png |right|link=http://opendmx.net/index.php/Download_%26_Install_OLA]]
[[Image:Llad_home.png| thumb |200px|right|Universe Settings]]
[[Image:Ola-rdm.png|thumb|200px|right|RDM Devices Page]]
[[Image:OLA_patching.png|thumb|200px|right|Drag & Drop RDM Patching]]
[[Image:Ola-mobile.png|thumb|200px|right|Mobile UI]]

__NOTOC__
The Open Lighting Architecture (OLA) is part of the [[Open Lighting Project]] and provides applications with a mechanism to send and receive [[DMX512]] & [[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.

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.

==Supported Protocols==

{| border=1 cellspacing="0"
! '''Protocol'''!! Linux !! '''Mac OS X''' || '''FreeBSD'''
|-
|| [[: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]]
|-
|| [[E1.31]] / [[ACN]] || [[Image:Green-tick.png|center]] || [[Image:Green-tick.png|center]] || [[Image:Green-tick.png|center]]
|-
|| [[:Category:ESP Net|ESP Net]] || [[Image:Green-tick.png|center]] || [[Image:Green-tick.png|center]] || [[Image:Green-tick.png|center]]
|-
|| [[OSC]] (Open Sound Control) || [[Image:Green-tick.png|center]] || [[Image:Green-tick.png|center]] || ?
|-
|| [[:Category:Pathport|Pathport]] || [[Image:Green-tick.png|center]] || [[Image:Green-tick.png|center]] || [[Image:Green-tick.png|center]]
|-
|| [[:Category:Sandnet|Sandnet]] || [[Image:Green-tick.png|center]] || [[Image:Green-tick.png|center]] || [[Image:Green-tick.png|center]]
|-
|| [[:Category:ShowNet|ShowNet]] || [[Image:Green-tick.png|center]] || [[Image:Green-tick.png|center]] || [[Image:Green-tick.png|center]]
|}

==Supported Devices==

{| border=1 cellspacing="0"
! '''Device'''!! Linux !! '''Mac OS X''' || '''FreeBSD'''
|-
|| [[Anyma uDMX]] || [[Image:Trans.gif|center]] || [[Image:Trans.gif|center]] || ?
|-
|| [[Arduino RGB Mixer]] || [[Image:Green-tick.png|center]] [[Image:Rdm.gif|center]] || [[Image:Green-tick.png|center]] [[Image:Rdm.gif|center]] || ?
|-
|| [[DMX 4 Linux]] || [[Image:Trans.gif|center]] || || ?
|-
|| [[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]]
|-
|| [[DMX-TRI]] || [[Image:Trans.gif|center]] || [[Image:Trans.gif|center]] || [[Image:Trans.gif|center]]
|-
|| [[DMXking USB DMX512-A]] || [[Image:Trans.gif|center]] [[Image:Recv.gif|center]] || [[Image:Trans.gif|center]] [[Image:Recv.gif|center]] || ?
|-
|| [[DMXter4 RDM]] / [[MiniDMXter]] || [[Image:Rdm.gif|center]] || [[Image:Rdm.gif|center]] || ?
|-
|| [[Eurolite USB DMX512 PRO]] || [[Image:Trans.gif|center]] || [[Image:Trans.gif|center]] || ?
|-
|| [[Open DMX USB]] || [[Image:Trans.gif|center]] || || ?
|-
|| [[Packetheads USB_DMX Dongle]] || [[Image:Green-tick.png|center]] || [[Image:Green-tick.png|center]] || ?
|-
|| [[RDM USB Pro]] || [[Image:Trans.gif|center]] [[Image:Recv.gif|center]] || [[Image:Trans.gif|center]] [[Image:Recv.gif|center]] || ?
|-
|| [[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]]
|-
|| [[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]] || ?
|-
|| [[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]] || ?
|-
|| [[StageProfi]] || [[Image:Trans.gif|center]] || [[Image:Trans.gif|center]] (Ethernet version only) || ?
|-
|| [http://machosehead.wordpress.com/2010/06/12/udmx_asp/ uDMX_asp] || [[Image:Trans.gif|center]] || [[Image:Trans.gif|center]] || ?
|-
|| [[ultraDMX Pro]] || [[Image:Trans.gif|center]] [[Image:Recv.gif|center]] || [[Image:Trans.gif|center]] [[Image:Recv.gif|center]] || ?
|-
|| [[ultraDMX Micro]] || [[Image:Trans.gif|center]] [[Image:Recv.gif|center]] || [[Image:Trans.gif|center]] [[Image:Recv.gif|center]] || ?
|-
|| [[USBDMX2]] || [[Image:Trans.gif|center]] || [[Image:Trans.gif|center]] || ?
|-
|| [http://www.soh.cz/produkty/modul-usb-dmx512 USB-DMX512] || [[Image:Trans.gif|center]] || [[Image:Trans.gif|center]] || ?
|-
|| [[Velleman K8062]] || [[Image:Trans.gif|center]] || [[Image:Trans.gif|center]] || ?
|-
|| [[Velleman_K8062_Upgrade|VX8062]] || [[Image:Trans.gif|center]] || [[Image:Trans.gif|center]] || ?
|}

==Getting Started==

Start here if you've never used OLA before and read these in order.
* [[Download & Install OLA]]
* [[Using OLA]] - A basic introduction
* [[OLA Command Line Tools]] - Documentation for the tools in ola-examples
* [[OLA Device Specific Configuration]]
* [[OLA Tips & Tricks]]
* [[RDM with OLA]]

<b>Tutorials</b>
* [[OLA on Windows with VMWare]]
* [[OLA Live CD]], instructions on how to use the Live CD
* [[OLA Raspberry Pi]]
* [[OLA on Beaglebone]]
* [[OlaOutput Max External]] - Setup OlaOutput on Mac OS X to send DMX messages from Max/MSP/Jitter
* [[OLAGuruPlug]] - Running OLA on a [http://www.globalscaletechnologies.com/c-4-guruplugs.aspx GuruPlug]
* [[OlaLED]] - control RGB LED via http
* [[OLA RDM Responder Testing]]

<b>Advanced Topics:</b>
* [[OLA Merging Algorithms]]
* [[OLA DiffServ support]] (QOS settings)
* [[OLA DMX Trigger]]

<b>Developer Documentation:</b>
* [[OLA developer info]] - about the source code and structure
* [[OLA Client API]] - the C++ API
* [[OLA Python API]] - easy DMX programming
* [[Build OLA Mac Packages]] - notes for building the .dmg images
* [[Building OLA for Windows]] - Notes on Windows support (in progress)
* [[Using OLA with Xcode]] - on a Mac, in Objective-C++
* [[Writing RDM Responder Tests]]
* [[Port Throttling]]
* [[OLA Performance Stats]]
* [[OLA TimeCode]]

<b>Tutorials</b>, these refer to the previous release but parts of them are still relevant.
* [[LLA Sandnet Tutorial]] - Setup Horizon using Sandnet and LLA
* [[LLA and Q Light Controller Ubuntu Tutorial]] - Setup LLA on Ubuntu/Debian-type distro with QLC
* [[LLA and Q Light Controller OSX Tutorial]] - Setup LLA on Mac OS X with QLC

[[Category:ArtNet]]
[[Category:ESP Net]]
[[Category:E1.31]]
[[Category:Sandnet]]
[[Category:ShowNet]]
[[Category:Utilities]]
[[Category:Pathport]]

OLA Raspberry Pi

2012-10-14T07:58:35Z

Mrpackethead: /* 3141 External DMX ports for use with OLA and Raspberry PI */

[[Image:Raspi_Colour_R.png|right]]

This tutorial describes how to get [[OLA]] running on the [http://www.raspberrypi.org/ Raspberry Pi]. The procedure described here is designed to get OLA up and running as fast as possible. If you don't trust the images below, or want to build everything from scratch, you can install an image from the [http://www.raspberrypi.org/downloads Raspberry Pi Site] and use the generic instructions for [[Download & Install OLA|Installing OLA]] on Linux.

There is plenty of information at the [http://elinux.org/RaspberryPiBoard Raspberry Pi Wiki]. The [http://www.raspberrypi.org/phpBB3/ Raspberry Pi Forum] is a good place to ask for help on Raspberry Pi specific issues.

__TOC__

= Getting Started=

You'll need the following:
* A Raspberry Pi board. See the [http://elinux.org/Buying_RPi Buying Guide] for how to purchase one.
* An SD card, greater or equal to 4GB. Check the [http://elinux.org/RPi_Verified_Peripherals#SD_cards SD Card Compatibility List] but don't worry too much if your card isn't listed there.
* An SD card reader. Make sure it supports the SDHC (high capacity) cards.
* A microUSB cable to provide power
* A CAT5 network cable.
* A Composite or HDMI monitor / TV to debug if things go wrong.
* A computer with a SSH Client and (optionally) Web Browser. You can use the Pi locally with a USB keyboard, but many people find it easier to access it from another machine.
* A powered USB Hub, if you plan on using a USB DMX/RDM device. Many devices draw more current than the Raspberry Pi can support. See the [http://groups.google.com/forum/?fromgroups=#!searchin/open-lighting/usb$20hub/open-lighting/mJpgweztVdE/pXm5SOihjmAJ discussion] on the Open Lighting Group for more details.

= Select your Image =

At this point you need to decide what image you want to use. The ''GIT Repo Image'' allows you to track the latest changes, but requires you to build the software yourself, which takes time. The ''Binary Package Image'' uses the pre-built binary packages for each release. The images are can be found [http://nomis52.net/data/raspi/ here].

We recommend the ''Binary Package Image'' if you're starting out.

==GIT Repo Image==

This tracks the [http://code.google.com/p/open-lighting/source/browse/ Git Repo], which means you can always use the very latest version of the code. The downside of using this option is that you have the build the code yourself (which takes time) and sometimes the code can break.

Download the latest ola-git-NNNNNNNN.zip image.

== Binary Package Image==

[http://www.raspbian.org/ Raspbian] is an armhf port of Debian specifically built for the Raspberry Pi. It offers slightly better performance than the stock Debian arm port.

Use this option if you prefer a more stable system. The pre-compiled packages are usually updated once a month and you don't need to spend time building OLA from source.

Download the latest raspbian-ola-X.Y.Z.zip image.

= Copying the Image =

Once you have selected an image, unzip it, and then you need to copy it to your SD card. The [http://elinux.org/RPi_Easy_SD_Card_Setup Raspberry Pi Wiki] page has detailed instructions for each platform.

This can take a while if you have a slow SD Card (see [http://en.wikipedia.org/wiki/Secure_Digital#Speed_Class_Rating SDHC Speeds]). On my Linux machine with a Class 2 card it took 14 minutes to write the 3.9G image, a Class 4 card took 11 minutes. On a Macbook Pro, using the onboard SD-Card slot it took 153 seconds to write the image using dd to a Class 4 card. Your speeds are likely to vary between machines.

= Starting Up =

Insert the card into the Raspberry Pi, make sure it's connected to a network which has a DHCP server running, and apply power. If you have a monitor attached you should see it booting. You'll then need to determine the IP address of your Pi. If you have a screen attached it should be shown just before the login prompt. Otherwise you can check your DHCP server logs and see which address was assigned. This example assumes an IP address of 192.168.1.200.

== Login using SSH ==

From your other machine, start your SSH client and SSH to your Pi. On Linux or Mac you can use the Terminal application and type:

<pre>
ssh pi@192.168.1.200
</pre>

The password is 'openlighting' (no quotes).

If you're on Windows you can download [http://www.chiark.greenend.org.uk/~sgtatham/putty/ PuTTY] and use that.

You should see the login message and get a shell prompt. If that doesn't work, you may need to restart (pull the power and plug it in again). Sometimes the Pi gets into a weird state on the first boot.

== Security ==

By default, the image comes with a SSH Key installed for Simon to access the system. If you trust me (and your probably do since you're running my code) you can leave this on. Otherwise you can delete my key by running:

<pre>
rm .ssh/authorized_keys
</pre>

Next change the password:

<pre>
passwd
Changing password for ola.
(current) UNIX password:
Enter new UNIX password:
Retype new UNIX password:
</pre>

== Enable Turbo Mode (Optional) ==

The Raspberry Pi supports overclocking, which can increase the performance of your system. You can configured this by running

<pre>
sudo raspi-config
</pre>

and then selecting the ''overclock'' option. I (Simon) normally run with the Turbo option and haven't experienced any problems.

== Expand the Root Partition (Optional) ==

If your SD card is larger than 4GB you can expand the root partition to use all of the available space. Again use

<pre>
sudo raspi-config
</pre>

and then choose the ''expand_rootfs'' option.

= Updating =

It's best to always use the latest version of OLA. Even immediately after downloding an image there may be updates to apply so we recommend you do this before you start using the Pi. To update your install follow one of the methods below, depending on what image you used.

== Git Repo ==

Once you're logged in, run:

<pre>
cd ola
git pull
autoreconf
./configure --enable-rdm-tests
make
sudo make install
</pre>

This can take a while.

== Binary Package Image ==

Run this:

<pre>
sudo apt-get update
sudo apt-get upgrade
</pre>

= Connecting to OLA =

At this point everything should be running. You can access the OLA web UI by opening a web browser and typing:

http://192.168.1.200:9090

Of course you should replace 192.168.1.200 with the IP Address of your device.

= Differences from the default Raspbian Image=

If you're interested in how these images differ from the image released by the Raspberry Pi Foundation, see [[Building a Custom Raspbian Image]]

= 3141 External DMX ports for use with OLA and Raspberry PI =

[[3141 Project]]

OLA Raspberry Pi

2012-10-14T07:57:52Z

Mrpackethead:

OLA DMX Trigger

2012-09-23T09:17:10Z

Mrpackethead: /* Sample Configs */

ola_trigger executes programs based on the values of DMX512 data. This allows a lighting console to trigger events on a computer, like playing music samples, advancing slides in presentations etc. . ola_trigger supports variable assignment, which offers a flexible way to control the behavior of the programs with the DMX512 data.

= Config File Syntax =

The config file defines the mapping of slot values to actions. Each line is a directive and directives are either ''action definitions'' or ''variable assignment''. The order of directives within the config file doesn't matter - actions are triggered in the order of their slot numbers.

Any characters between a '#' and the end of the line are comments and are ignored.

== Action Definitions ==

Action definitions are specified one per line, in the following form:

<pre>
[Slot Number] [Slot Values] [Action]
</pre>

The columns must be separated by whitespace.

=== Slot Number ===

The first column, slot number, specifies the DMX512 slot the action is valid for. Slot numbers range from 0 to 511. Slot numbers may be offset by using the --offset option (see the Usage section below).

=== Slot Values ===

The second column controls which DMX512 values trigger the action. Slot values range from 0 to 255. Multiple values are separated by commas. Ranges can be specified with a hyphen.

<pre>
1,2,3,4 # Values 1 through to 4
1-4,10-14 # Values 1 to 4 and 10 to 14 (inclusive)
</pre>

The % character the is default match. It triggers for all values that don't have an explicit action configured

<pre>
0-100 # Values 0 to 100
% # Triggers for everything else (101 - 255)
</pre>

Actions are only triggered when the value changes. In the example above, if the value of slot 0 in the previous frame was 10, and a frame with slot 0 @ 10 arrived, the action will not be triggered. If a frame with slot 0 @ 5 arrives, the action will trigger again.

=== Actions ===

The third column specifies the action to run. Actions can be either variable assignments or commands and can trigger on rising values, falling values or both.

==== Variable Assignment ====

Variables can be assigned values which can then be used in later commands. Variable assignments are in the form

<pre>
variable=value
</pre>

The value must be quoted if it contains whitespace:

<pre>
variable="a quoted value"
</pre>

==== Commands ====

Commands are enclosed in back ticks (`). Command arguments are separated by whitespace, quotes can be used with arguments that contain whitespace.

<pre>
`echo hello world` # Execute the '''echo''' command with two arguments [hello, world]
`echo "hello world"` # Execute the '''echo''' command with single argument "hello world".
</pre>

Variables are specified with ${ }.

<pre>
`echo ${foo}` # Run echo with the value of the foo variable.
</pre>

Variables can be nested, which means you can do things like

<pre>
# if i=1 and count_1=foo
`echo ${count_${i}}` # runs echo foo
</pre>

==== Rising / Falling Triggering ====

Commands can be specified to trigger only if the value rises or falls. This is done with the + and - symbols:

<pre>
+`echo rising edge` -`echo falling edge`
</pre>

Either the rising or falling command can be omitted, in that case no action will be taken.

=== Full Action Definition Example ===

Putting everything together, the following will run `echo hello world` whenever the value of the first DMX slot changes to 0, 5 or 10.

<pre>
0 0,5,10 `echo hello world`
</pre>

== Variables ==

Variables can be assigned default values using the same syntax as variable assignment actions:

<pre>
# set the default value of foo
foo=bar
</pre>

=== Special Variables ===

The variables ${slot_offset} and ${slot_value} are available for use within commands. For example:

<pre>
0 % `echo "Slot ${slot_offset} is at ${slot_value}"`
</pre>

You should always use ${slot_offset} rather than hard coding slot numbers within command definitions, since the slot number may change with the --offset option.

= Usage =

Before running ola_trigger, make sure that olad is running and the universe has been configured with a DMX512 source. The config file is provided on the command line:

<pre>
ola_trigger example.conf
</pre>

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

= Sample Configs =

Sample configs are provided in the [http://code.google.com/p/linux-lighting/source/browse/#git%2Ftools%2Fola_trigger%2Fcontrib tools/ola_trigger/contrib] directory.

A full example config is provided in the tools/ola_trigger directory. If you have configs that may be useful to others please submit them.

[[Rasberry PI Media Player]] A combination of a Raspberry PI, ola_trigger and omxplayer

OLA Raspberry Pi

2012-09-16T18:44:43Z

Mrpackethead: /* Debian Packages */

[[Image:Raspi_Colour_R.png|right]]

This tutorial describes how to get [[OLA]] running on the [http://www.raspberrypi.org/ Raspberry Pi]. The procedure described here is designed to get OLA up and running as fast as possible. If you don't trust the images below, or want to build everything from scratch, you can install an image from the [http://www.raspberrypi.org/downloads Raspberry Pi Site] and use the generic instructions for [[Download & Install OLA|Installing OLA]] on Linux.

There is plenty of information at the [http://elinux.org/RaspberryPiBoard Raspberry Pi Wiki]. The [http://www.raspberrypi.org/phpBB3/ Raspberry Pi Forum] is a good place to ask for help on Raspberry Pi specific issues.

__TOC__

= Getting Started=

You'll need the following:
* A Raspberry Pi board. The [http://elinux.org/Buying_RPi Buying Guide]
* An SD card. Check the [http://elinux.org/RPi_Verified_Peripherals#SD_cards SD Card Compatibility List] but don't worry too much if your card isn't listed there. A 4GB card should be more than sufficient.
* An SD card reader. Make sure it supports the SDHC (high capacity) cards.
* A microUSB cable to provide power
* A CAT5 network cable.
* A Composite or HDMI monitor / TV to debug if things go wrong.
* A computer with a SSH Client and (optionally) Web Browser. You can use the Pi locally with a USB keyboard, but many people find it easier to access it from another machine.

= Select your Image =

At this point you need to decide what version of OLA you want to use. Images are [http://nomis52.net/data/raspi/ here].

==GIT Repo==

This tracks the [http://code.google.com/p/open-lighting/source/browse/ Git Repo], which means you can always use the very latest version of the code. The downside of using this option is that you have the build the code yourself (which takes time) and sometimes the code can break.

Download the latest ola-git-NNNNNNNN.zip image.

==Debian (Raspbian) Packages==

[http://www.raspbian.org/ Raspbian] is an armhf port of Debian specifically built for the Raspberry Pi. It offers slightly better performance than the stock Debian arm port.

Use this option if you prefer a more stable system. The pre-compiled packages are usually updated once a month and you don't need to spend time building OLA from source.

Download the latest raspbian-ola-X.Y.Z.zip image. The debian-ola-xxxx images are now depreciated.

If you're interested in the actual Debian packages (if you're building your own image from scratch) there are located [http://apt.openlighting.org/debian/ here].

= Copying the Image =

Once you have selected an image, unzip it, and then you need to copy it to your SD card. The [http://elinux.org/RPi_Easy_SD_Card_Setup Raspberry Pi Wiki] page has detailed instructions for each platform.

This can take a while if you have a slow SD Card (see [http://en.wikipedia.org/wiki/Secure_Digital#Speed_Class_Rating SDHC Speeds]). On my Linux machine with a Class 2 card it took 14 minutes to write the 3.9G image, a Class 4 card took 11 minutes. On Mrpacketheads Macbook Pro, using the onboard SD-Card slot it took 153 seconds to write the image using dd to a Class 4 card. Your speeds are likely to vary between machines.

= Starting Up =

Insert the card into the Raspberry Pi, make sure it's connected to a network which has a DHCP server running, and apply power. If you have a monitor attached you should see it booting. You'll then need to determine the IP address of your Pi. If you have a screen attached it should be shown just before the login prompt. Otherwise you can check your DHCP server logs and see which address was assigned. This example assumes an IP address of 192.168.1.200.

== Login using SSH ==

From your other machine, start your SSH client and SSH to your Pi. On Linux or Mac you can use the Terminal application and type:

<pre>
ssh ola@192.168.1.200
</pre>

The password is 'openlighting' (no quotes).

If you're on Windows you can download [http://www.chiark.greenend.org.uk/~sgtatham/putty/ PuTTY] and use that.

You should see the login message and get a shell prompt. If that doesn't work, you may need to restart (pull the power and plug it in again). Sometimes the Pi gets into a weird state on the first boot.

== Security ==

By default, the image comes with a SSH Key installed for Simon to access the system. If you trust me (and your probably do since you're running my code) you can leave this on. Otherwise you can delete my key by running:

<pre>
rm .ssh/authorized_keys
</pre>

Next change the password:

<pre>
passwd
Changing password for ola.
(current) UNIX password:
Enter new UNIX password:
Retype new UNIX password:
</pre>

== Resizing the Root Partition ==

If you're using a Raspbian based image (which you should be) there is a script raspi-config which you can use manage your system. This script can resize the partitions on the SD card so if you're using a card more than 2G you can make use of all the space. To run it type:

<pre>
sudo raspi-config
</pre>

and then choose the 'expand_rootfs' option.

= Updating =

It's best to always use the latest version of OLA. To update your install follow one of the methods below, depending on what image you used.

== Git Repo ==

Once you're logged in, run:

<pre>
cd ola
git pull
autoreconf
./configure --enable-rdm-tests
make
sudo make install
</pre>

This can take a while.

== Raspbian Packages ==

Run this:

<pre>
sudo apt-get update
sudo apt-get upgrade
</pre>

= Differences from the default Debian Image=

Here are the differences from the default Debian squeeze image. If you create your own install from scratch you probably want to do these as well.

* Many unused packages have been removed (samba, X, mysql, nfs etc.)
* OLA dependancies have been installed (microhttpd, libusb, etc.)
* The OLA git repo has been cloned into /home/ola/ola
* The pi account has been removed
* Root ssh access has been disabled
* The ola account was added and added to the dialout & plugdev groups
* /etc/rc.local has been modified to regenerate the ssh keys on the first boot
* Various other accounts have been removed (pnd, tli, buildbot etc.).
* Timezone changed to US/Pacific
* /etc/udev/rules.d/10-local.rules was updated according to [[OLA_Device_Specific_Configuration]]

OLA Raspberry Pi

2012-09-16T03:14:46Z

Mrpackethead: /* Copying the Image */

[[Image:Raspi_Colour_R.png|right]]

This tutorial describes how to get [[OLA]] running on the [http://www.raspberrypi.org/ Raspberry Pi]. The procedure described here is designed to get OLA up and running as fast as possible. If you don't trust the images below, or want to build everything from scratch, you can install an image from the [http://www.raspberrypi.org/downloads Raspberry Pi Site] and use the generic instructions for [[Download & Install OLA|Installing OLA]] on Linux.

There is plenty of information at the [http://elinux.org/RaspberryPiBoard Raspberry Pi Wiki]. The [http://www.raspberrypi.org/phpBB3/ Raspberry Pi Forum] is a good place to ask for help on Raspberry Pi specific issues.

__TOC__

= Getting Started=

You'll need the following:
* A Raspberry Pi board. The [http://elinux.org/Buying_RPi Buying Guide]
* An SD card. Check the [http://elinux.org/RPi_Verified_Peripherals#SD_cards SD Card Compatibility List] but don't worry too much if your card isn't listed there. A 4GB card should be more than sufficient.
* An SD card reader. Make sure it supports the SDHC (high capacity) cards.
* A microUSB cable to provide power
* A CAT5 network cable.
* A Composite or HDMI monitor / TV to debug if things go wrong.
* A computer with a SSH Client and (optionally) Web Browser. You can use the Pi locally with a USB keyboard, but many people find it easier to access it from another machine.

= Select your Image =

At this point you need to decide what version of OLA you want to use. Images are [http://nomis52.net/data/raspi/ here].

==GIT Repo==

This tracks the [http://code.google.com/p/open-lighting/source/browse/ Git Repo], which means you can always use the very latest version of the code. The downside of using this option is that you have the build the code yourself (which takes time) and sometimes the code can break.

Download the latest ola-git-NNNNNNNN.zip image.

==Debian Packages==

The Debian Packages are built using Raspbian which is a customised debian environment for use on the Rasberry PI.

Use this option if you prefer a more stable system. The packages are usually updated once a month or so and you don't need to spend time building OLA from source.

Download the latest raspbian-ola-X.Y.Z.zip image.

The debian-ola-xxxx images are now depreciated.

If you're interested in the actual Debian packages (if you're building your own image from scratch) there are located [http://apt.openlighting.org/debian/ here].

= Copying the Image =

Once you have selected an image, unzip it, and then you need to copy it to your SD card. The [http://elinux.org/RPi_Easy_SD_Card_Setup Raspberry Pi Wiki] page has detailed instructions for each platform.

This can take a while if you have a slow SD Card (see [http://en.wikipedia.org/wiki/Secure_Digital#Speed_Class_Rating SDHC Speeds]). On my Linux machine with a Class 2 card it took 14 minutes to write the 3.9G image, a Class 4 card took 11 minutes. On Mrpacketheads Macbook Pro, using the onboard SD-Card slot it took 153 seconds to write the image using dd to a Class 4 card. Your speeds are likely to vary between machines.

= Starting Up =

Insert the card into the Raspberry Pi, make sure it's connected to a network which has a DHCP server running, and apply power. If you have a monitor attached you should see it booting. You'll then need to determine the IP address of your Pi. If you have a screen attached it should be shown just before the login prompt. Otherwise you can check your DHCP server logs and see which address was assigned. This example assumes an IP address of 192.168.1.200.

== Login using SSH ==

From your other machine, start your SSH client and SSH to your Pi. On Linux or Mac you can use the Terminal application and type:

<pre>
ssh ola@192.168.1.200
</pre>

The password is 'openlighting' (no quotes).

If you're on Windows you can download [http://www.chiark.greenend.org.uk/~sgtatham/putty/ PuTTY] and use that.

You should see the login message and get a shell prompt. If that doesn't work, you may need to restart (pull the power and plug it in again). Sometimes the Pi gets into a weird state on the first boot.

== Security ==

By default, the image comes with a SSH Key installed for Simon to access the system. If you trust me (and your probably do since you're running my code) you can leave this on. Otherwise you can delete my key by running:

<pre>
rm .ssh/authorized_keys
</pre>

Next change the password:

<pre>
passwd
Changing password for ola.
(current) UNIX password:
Enter new UNIX password:
Retype new UNIX password:
</pre>

= Updating =

It's best to always use the latest version of OLA. To update your install follow one of the methods below, depending on what image you used.

== Git Repo ==

Once you're logged in, run:

<pre>
cd ola
git pull
autoreconf
./configure --enable-rdm-tests
make
sudo make install
</pre>

This can take a while.

== Debian Packages ==

Run this:

<pre>
sudo apt-get update
sudo apt-get upgrade
</pre>

= Differences from the default Debian Image=

Here are the differences from the default Debian squeeze image. If you create your own install from scratch you probably want to do these as well.

* Many unused packages have been removed (samba, X, mysql, nfs etc.)
* OLA dependancies have been installed (microhttpd, libusb, etc.)
* The OLA git repo has been cloned into /home/ola/ola
* The pi account has been removed
* Root ssh access has been disabled
* The ola account was added and added to the dialout & plugdev groups
* /etc/rc.local has been modified to regenerate the ssh keys on the first boot
* Various other accounts have been removed (pnd, tli, buildbot etc.).
* Timezone changed to US/Pacific
* /etc/udev/rules.d/10-local.rules was updated according to [[OLA_Device_Specific_Configuration]]

OLA Raspberry Pi

2012-09-16T03:12:03Z

Mrpackethead: /* Debian Packages */

[[Image:Raspi_Colour_R.png|right]]

This tutorial describes how to get [[OLA]] running on the [http://www.raspberrypi.org/ Raspberry Pi]. The procedure described here is designed to get OLA up and running as fast as possible. If you don't trust the images below, or want to build everything from scratch, you can install an image from the [http://www.raspberrypi.org/downloads Raspberry Pi Site] and use the generic instructions for [[Download & Install OLA|Installing OLA]] on Linux.

There is plenty of information at the [http://elinux.org/RaspberryPiBoard Raspberry Pi Wiki]. The [http://www.raspberrypi.org/phpBB3/ Raspberry Pi Forum] is a good place to ask for help on Raspberry Pi specific issues.

__TOC__

= Getting Started=

You'll need the following:
* A Raspberry Pi board. The [http://elinux.org/Buying_RPi Buying Guide]
* An SD card. Check the [http://elinux.org/RPi_Verified_Peripherals#SD_cards SD Card Compatibility List] but don't worry too much if your card isn't listed there. A 4GB card should be more than sufficient.
* An SD card reader. Make sure it supports the SDHC (high capacity) cards.
* A microUSB cable to provide power
* A CAT5 network cable.
* A Composite or HDMI monitor / TV to debug if things go wrong.
* A computer with a SSH Client and (optionally) Web Browser. You can use the Pi locally with a USB keyboard, but many people find it easier to access it from another machine.

= Select your Image =

At this point you need to decide what version of OLA you want to use. Images are [http://nomis52.net/data/raspi/ here].

==GIT Repo==

This tracks the [http://code.google.com/p/open-lighting/source/browse/ Git Repo], which means you can always use the very latest version of the code. The downside of using this option is that you have the build the code yourself (which takes time) and sometimes the code can break.

Download the latest ola-git-NNNNNNNN.zip image.

==Debian Packages==

The Debian Packages are built using Raspbian which is a customised debian environment for use on the Rasberry PI.

Use this option if you prefer a more stable system. The packages are usually updated once a month or so and you don't need to spend time building OLA from source.

Download the latest raspbian-ola-X.Y.Z.zip image.

The debian-ola-xxxx images are now depreciated.

If you're interested in the actual Debian packages (if you're building your own image from scratch) there are located [http://apt.openlighting.org/debian/ here].

= Copying the Image =

Once you have selected an image, unzip it, and then you need to copy it to your SD card. The [http://elinux.org/RPi_Easy_SD_Card_Setup Raspberry Pi Wiki] page has detailed instructions for each platform.

This can take a while if you have a slow SD Card (see [http://en.wikipedia.org/wiki/Secure_Digital#Speed_Class_Rating SDHC Speeds]). On my Linux machine with a Class 2 card it took 14 minutes to write the 3.9G image, a Class 4 card took 11 minutes.

= Starting Up =

Insert the card into the Raspberry Pi, make sure it's connected to a network which has a DHCP server running, and apply power. If you have a monitor attached you should see it booting. You'll then need to determine the IP address of your Pi. If you have a screen attached it should be shown just before the login prompt. Otherwise you can check your DHCP server logs and see which address was assigned. This example assumes an IP address of 192.168.1.200.

== Login using SSH ==

From your other machine, start your SSH client and SSH to your Pi. On Linux or Mac you can use the Terminal application and type:

<pre>
ssh ola@192.168.1.200
</pre>

The password is 'openlighting' (no quotes).

If you're on Windows you can download [http://www.chiark.greenend.org.uk/~sgtatham/putty/ PuTTY] and use that.

You should see the login message and get a shell prompt. If that doesn't work, you may need to restart (pull the power and plug it in again). Sometimes the Pi gets into a weird state on the first boot.

== Security ==

By default, the image comes with a SSH Key installed for Simon to access the system. If you trust me (and your probably do since you're running my code) you can leave this on. Otherwise you can delete my key by running:

<pre>
rm .ssh/authorized_keys
</pre>

Next change the password:

<pre>
passwd
Changing password for ola.
(current) UNIX password:
Enter new UNIX password:
Retype new UNIX password:
</pre>

= Updating =

It's best to always use the latest version of OLA. To update your install follow one of the methods below, depending on what image you used.

== Git Repo ==

Once you're logged in, run:

<pre>
cd ola
git pull
autoreconf
./configure --enable-rdm-tests
make
sudo make install
</pre>

This can take a while.

== Debian Packages ==

Run this:

<pre>
sudo apt-get update
sudo apt-get upgrade
</pre>

= Differences from the default Debian Image=

Here are the differences from the default Debian squeeze image. If you create your own install from scratch you probably want to do these as well.

* Many unused packages have been removed (samba, X, mysql, nfs etc.)
* OLA dependancies have been installed (microhttpd, libusb, etc.)
* The OLA git repo has been cloned into /home/ola/ola
* The pi account has been removed
* Root ssh access has been disabled
* The ola account was added and added to the dialout & plugdev groups
* /etc/rc.local has been modified to regenerate the ssh keys on the first boot
* Various other accounts have been removed (pnd, tli, buildbot etc.).
* Timezone changed to US/Pacific
* /etc/udev/rules.d/10-local.rules was updated according to [[OLA_Device_Specific_Configuration]]