Talk:Open Lighting Architecture - Revision history

Nomis52: moved Talk:OLA to Talk:Open Lighting Architecture

2010-03-01T17:58:21Z

moved Talk:OLA to Talk:Open Lighting Architecture

Nomis52 at 21:40, 8 August 2009

2009-08-08T21:40:37Z

Nomis52 at 21:29, 8 August 2009

2009-08-08T21:29:01Z

Nomis52: moved Talk:LLA to Talk:OLA: Project name changed to OLA

2009-07-26T05:24:18Z

moved Talk:LLA to Talk:OLA: Project name changed to OLA

Beier: removed what became tha page "LLA developer info"

2008-11-14T13:48:40Z

removed what became tha page "LLA developer info"

Beier: driver matrix

2008-11-13T15:53:15Z

driver matrix

Beier: new suggestions

2008-11-13T11:48:02Z

new suggestions

Beier: New page: There are software tools specific for the interface "Enttec DMX USB Pro", also in [LLA]. Where should the be described? On a separate page, with links from LLA and Using LLA?

2008-07-17T13:00:54Z

New page: There are software tools specific for the interface "Enttec DMX USB Pro", also in [LLA]. Where should the be described? On a separate page, with links from LLA and Using LLA?

New page

There are software tools specific for the interface "Enttec DMX USB Pro", also in [LLA]. Where should the be described? On a separate page, with links from [[LLA]] and [[Using LLA]]?

← Older revision		Revision as of 21:40, 8 August 2009
Line 1:		Line 1:
−	~~There are software tools specific for the interface "Enttec DMX USB Pro", also in [LLA]. Where should they be described? On a separate page, with links from [[LLA]] and [[Using LLA]]?~~
−
−	* How to use them (take info from nomis52.net and elaborate them (Se the example with lla_usbpro below).

	* developer info: the structure of function calls and data flow.		* developer info: the structure of function calls and data flow.

← Older revision		Revision as of 21:29, 8 August 2009
Line 8:		Line 8:

	* llad only detects USB Pro devices when the daemon is started. If the USB device is unplugged, it must be plugged in befor llad is started again.		* llad only detects USB Pro devices when the daemon is started. If the USB device is unplugged, it must be plugged in befor llad is started again.
−
−	~~Example:~~
−	~~=== lla_usbpro ===~~
−
−	~~This can "Query and control the parameters of the [[DMX USB Pro\|Enttec USB Pro]] device".~~
−
−	~~Options:~~
−	* -d, --dev <dev_id> The device id to configure. (required?)
−
−	* -p, --params Get and show the parameters.
−	* -s, --serial Get and show the serial number.
−
−	* -b, --brk <brk> Set the break time. ''what is the unit?''
−	* -m, --mab <mab> Set the make after-break-time. ''what is the unit?''
−	* -r, --rate <rate> Set the transmission rate. Unit is ''DMX Packets per second'', from 1 to 40, "0" means "fastest possible".
−	* -s, --serial Get the serial number.

@@ Line 1: / Line 1: @@
 There are software tools specific for the interface "Enttec DMX USB Pro", also in [LLA]. Where should they be described? On a separate page, with links from [[LLA]] and [[Using LLA]]?
-* How to use them (take info from nomis52.net and elaborate them (Se the exaple with lla_usbpro below).
+* How to use them (take info from nomis52.net and elaborate them (Se the example with lla_usbpro below).
 * developer info: the structure of function calls and data flow.
     Does lla_usbpro write arbitrary settings to the device if it cannot read valid data back?
     i.e. does LLA store the garbled numbers and write them back to the "USB Pro"? Is there a boundary check on the values?
 Example:
 === lla_usbpro ===
-Query and control the parameters of the [[DMX USB Pro|Enttec USB Pro]] device
+This can "Query and control the parameters of the [[DMX USB Pro|Enttec USB Pro]] device".
 Options:
@@ Line 21: / Line 23: @@
 * -m, --mab <mab> Set the make after-break-time. ''what is the unit?''
 * -r, --rate <rate> Set the transmission rate. Unit is ''DMX Packets per second'', from 1 to 40, "0" means "fastest possible".
 * -s, --serial Get the serial number.

← Older revision		Revision as of 15:53, 13 November 2008
Line 34:		Line 34:
	* What is it with the hidden web server?		* What is it with the hidden web server?
	How is functionality split between the usbpro plugin and the example program?		How is functionality split between the usbpro plugin and the example program?
		+
		+	== Drivers and platforms ==
		+	LLA compiles on Linux and Mac and probably also Windows, but not all drivers work everywhere (yet). Here the status can be listed.
		+
		+	<b>Supported Devices/Protocols:</b>
		+	{\| border=1
		+	! '''Driver'''!! Linux !! '''Mac OS X''' !! '''Windows'''
		+	\|-
		+	\|\| [[:Category:ArtNet\|ArtNet]] \|\| Linux=Yes \|\| ?? \|\| ??
		+	\|-
		+	\|\| [[:Category:ShowNet\|ShowNet]] \|\| Linux=Yes \|\| ?? \|\| ??
		+	\|-
		+	\|\| [[:Category:ESP Net\|ESP Net]] \|\| Linux=Yes \|\| ?? \|\| ??
		+	\|-
		+	\|\| [[:Category:Sandnet\|Sandnet]] \|\| Linux=Yes \|\| ?? \|\| ??
		+	\|-
		+	\|\| [[DMX USB Pro]] \|\| Linux=Yes \|\| ?? \|\| No
		+	\|-
		+	\|\| [[Open DMX USB]] 1) \|\| Linux=Yes \|\| ?? \|\| No
		+	\|-
		+	\|\| [[DMX 4 Linux]] \|\| Linux=Yes \|\| ?? \|\| No
		+	\|-
		+	\|\| [[StageProfi]] \|\| Linux=Yes \|\| ?? \|\| No
		+	\|-
		+	\|\| [[:Category:Pathport\|Pathport]] \|\| Linux=in testing \|\| ?? \|\| No
		+	\|-
		+	\|\| [[E1.31]] / [[ACN]] \|\| Linux=development started \|\| ?? \|\| No
		+	\|}
		+
		+	Note 1): Support through the [http://www.erwinrol.com/index.php?opensource/dmxusb.php Linux kernel module from Erwin Rol], as detailed in [[LLA, OpenDMX USB and Q Light Controller Tutorial]].
		+
		+	Unsupported devices:
		+	* [[Peperoni]] [[Rodin1]] (but this is supported directly by [[QLC]]
		+	* [[Peperoni]] [[USBDMX21]]
		+	* [[Anyma uDMX]
		+	* [[USB DMX]]
		+	* [[Sandsys]] [[UMX2]]
		+	* [[Sandsys]] [[UMX4]]
		+	* [[Velleman K8062]] (no developer info available?)

← Older revision		Revision as of 11:48, 13 November 2008
Line 1:		Line 1:
−	There are software tools specific for the interface "Enttec DMX USB Pro", also in [LLA]. Where should ~~the~~ be described? On a separate page, with links from [[LLA]] and [[Using LLA]]?	+	There are software tools specific for the interface "Enttec DMX USB Pro", also in [LLA]. Where should they be described? On a separate page, with links from [[LLA]] and [[Using LLA]]?
		+
		+	* How to use them (take info from nomis52.net and elaborate them (Se the exaple with lla_usbpro below).
		+	* developer info: the structure of function calls and data flow.
		+	Does lla_usbpro write arbitrary settings to the device if it cannot read valid data back?
		+	i.e. does LLA store the garbled numbers and write them back to the "USB Pro"? Is there a boundary check on the values?
		+
		+
		+	Example:
		+	=== lla_usbpro ===
		+
		+	Query and control the parameters of the [[DMX USB Pro\|Enttec USB Pro]] device
		+
		+	Options:
		+	* -d, --dev <dev_id> The device id to configure. (required?)
		+
		+	* -p, --params Get and show the parameters.
		+	* -s, --serial Get and show the serial number.
		+
		+	* -b, --brk <brk> Set the break time. ''what is the unit?''
		+	* -m, --mab <mab> Set the make after-break-time. ''what is the unit?''
		+	* -r, --rate <rate> Set the transmission rate. Unit is ''DMX Packets per second'', from 1 to 40, "0" means "fastest possible".
		+	* -s, --serial Get the serial number.
		+
		+
		+	= LLA developer info =
		+	Would it be nice with a page with this name? Or perhaps LLA code documentation?
		+
		+	Suggestions for content:
		+	* I have difficulties to track the flow of data from it is fetched from the USB Pro until it is printed to the console by the app lla_usbpro. Some diagrams over the structure and data flow diagrams, or text that gives a good overview would be nice
		+	* What is the structure of the plugins?
		+	* What is the interface between the LLA core and LLA plugins?
		+	* What is the interface between the LLA core and other apps/clients to LLA like QLC?
		+	* What is it with the hidden web server?
		+	How is functionality split between the usbpro plugin and the example program?

← Older revision	Revision as of 17:58, 1 March 2010
(No difference)

← Older revision	Revision as of 05:24, 26 July 2009
(No difference)