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 "OLA Device Specific Configuration"
From wiki.openlighting.org
(→Open DMX USB: update udev rule) |
m (→Linux) |
||
Line 37: | Line 37: | ||
<pre> | <pre> | ||
+ | # udev rules for ftdi devices | ||
SUBSYSTEM=="usb|usb_device", ACTION=="add", ATTRS{idVendor}=="0403", ATTRS{idProduct}=="6001", GROUP="plugdev" | SUBSYSTEM=="usb|usb_device", ACTION=="add", ATTRS{idVendor}=="0403", ATTRS{idProduct}=="6001", GROUP="plugdev" | ||
</pre> | </pre> |
Revision as of 21:51, 8 September 2012
Contents
Anyma
Linux
You need a udev rule like this in /etc/udev/rules.d/10-local.rules
# udev rules file for the anyma dmx device SUBSYSTEM=="usb|usb_device", ACTION=="add", ATTRS{idVendor}=="16c0", ATTRS{idProduct}=="05dc", GROUP="plugdev"
ArtNet
If you've having problems sending ArtNet data is may be because your receivers don't support ArtNet II and/or send ArtPollReply messages. You can force OLA to always broadcast data by changing ~/.ola/ola-artnet.conf to contain:
always_broadcast = true
Eurolite USB DMX512 PRO
Linux
Sometime the cdc_acm kernel module claims the device. If this happens you'll see errors like "Cannot claim device" and/or "another process has device opened for exclusive access". To avoid this you can remove the module (rmmod). A udev rule like what is used for the Anyma device should also work.
Mac
Install the KEXT.
Open DMX USB / FTDI RS485
There are two options, the 'Open DMX' plugin that requires the kernel module and the native FTDI driver.
Linux
If you're using the FTDI Driver, you need to have libftdi-dev installed before you run ./configure. You also need to add the following udev rule
# udev rules for ftdi devices SUBSYSTEM=="usb|usb_device", ACTION=="add", ATTRS{idVendor}=="0403", ATTRS{idProduct}=="6001", GROUP="plugdev"
StageProfi
This comes in two flavors, a USB model and an Ethernet/IP model.
device = /dev/ttyUSB0 device = 192.168.1.250
USB Pro
Mac
Make sure you install the drives: http://www.ftdichip.com/Drivers/VCP.htm
After a restart run:
ls /dev/cu.usbserial-*
Make sure your ~/.ola/ola-usbpro.conf file matches the path above:
device_dir = /dev device_prefix = ttyUSB device_prefix = cu.usbserial-
i.e. Look for devices at /dev/ttyUSB* , /dev/cu.usbserial-*
OLA also comes with a tool to update the firmware on a USB Pro:
./tools/usbpro_firmware -d /dev/cu.usbserial-0000101D -f <firmware_file>
USBDMX2
Linux
You need a udev rule like this in /etc/udev/rules.d/10-local.rules
# udev rules file for the usbdmx2 dmx device SUBSYSTEM=="usb|usb_device", ACTION=="add", ATTRS{idVendor}=="0962", GROUP="plugdev"
There is an issue where the device isn't detected correctly the first time. You may need to restart OLA once the DMX Transmit led comes on.
Mac
There is an issue where the device isn't detected correctly the first time. You may need to restart OLA once the DMX Transmit led comes on.
Velleman VM166 / K8062
Mac
If you're installed from source you'll need the codeless KEXT which is available here. If you installed OLA from the mac binary package this is already included.
Linux
You need a udev rule like this in /etc/udev/rules.d/10-local.rules
# udev rules file for the velleman dmx device SUBSYSTEM=="usb|usb_device", ACTION=="add", ATTRS{idVendor}=="10cf", ATTRS{idProduct}=="8062", GROUP="plugdev"
Then make sure the user olad runs as is a member of plugdev.