Personal tools
The Open Lighting Project has moved!

We've launched our new site at www.openlighting.org. This wiki will remain and be updated with more technical information.

Difference between revisions of "Talk:Open Lighting Architecture"

From wiki.openlighting.org

Jump to: navigation, search
(new suggestions)
 
(5 intermediate revisions by 2 users not shown)
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).
 
 
* developer info: the structure of function calls and data flow.
 
* 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?
 
   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?
 
   i.e. does LLA store the garbled numbers and write them back to the "USB Pro"? Is there a boundary check on the values?
  
 
+
* 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 ===
 
 
 
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?
 

Latest revision as of 10:58, 1 March 2010

  • 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?
  • 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.