Q Light Controller+

Posted: **Sat Jul 04, 2015 10:06 pm**

Hi, my name is Claudio and i'm a new enthusiast of lighting software. A couple of year ago i'd buyed a USB-to-DMX interface that works great with freestyler on windows, but now i would like to move to Linux and hopely find your software. I think that my problem is that my device isn't supported, been more specific i have a USB DMX512 of manufacter OKSID, here's what my log shows when i plug it:

Code: Select all

Jul  4 18:27:06 nfstation kernel: [36222.501356] usb 3-1: new low-speed USB device number 6 using xhci_hcd
Jul  4 18:27:06 nfstation kernel: [36222.523088] usb 3-1: New USB device found, idVendor=0403, idProduct=e088
Jul  4 18:27:06 nfstation kernel: [36222.523095] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jul  4 18:27:06 nfstation kernel: [36222.523098] usb 3-1: Product: USB DMX512
Jul  4 18:27:06 nfstation kernel: [36222.523101] usb 3-1: Manufacturer: OksiD
Jul  4 18:27:06 nfstation kernel: [36222.523104] usb 3-1: SerialNumber: ########
Jul  4 18:27:06 nfstation kernel: [36222.523302] xhci_hcd 0000:00:14.0: xHCI xhci_add_endpoint called with enabled ep ffff8800ac4f3740
Jul  4 18:27:06 nfstation mtp-probe: checking bus 3, device 6: "/sys/devices/pci0000:00/0000:00:14.0/usb3/3-1"
Jul  4 18:27:06 nfstation mtp-probe: bus: 3, device: 6 was not an MTP device

But when i go to the input/output section of the QLC+ doesn't show it on the list.

Any clue of what is happening?

Thanks in advanced!

Posted: **Sun Jul 05, 2015 9:02 am**

Hello Claudio,
that is interesting...according to the Linux USB IDs (http://www.linux-usb.org/usb.ids) your device is FTDI, but the product is not listed as "known" by Linux.

From the dmesg messages, it seems linux doesn't even map it to a /dev/ttyUSB device.
QLC+ recognizes the "standard" FTDI chip-based devices as vendor: 0x0403 product: 0x6001 and a few more (like DMX4ALL products)

If you build from sources, you can try adding your product ID to the list of devices to search, and see if libFTDI does the rest. Hopefully it will.
If you need help in doing that, just ask. Please also share which distribution you're using (and also 32 or 64bit) and a link to the DMX adapter page.

The reason why Freestyler works is that Windows needs drivers, so probably FS looks for "serial converter" devices and works seamlessly with them.

Posted: **Mon Jul 06, 2015 12:02 pm**

Hello Massimo, thanks for your quick answer.

I will take the chance of building from sources, i was reading the docs and it's very clear. I think that the only thing i will need is the file within the sources where i have to add my product ID.

Now talking about my device, it was hard to find the web of the manufacter or the adapter page, but a presume that this is the closest thing i've found:

http://www.oksid.ch/

Here's my Enviroment Details:

Distribution Details:

Code: Select all

Distributor ID:	Ubuntu
Description:	Ubuntu 14.04.2 LTS 64 bits
Release:	        14.04
Codename:	trusty

Hardware Details:

Code: Select all

Memory: 8gb
Processor: Intel® Core™ i7-3630QM CPU @ 2.40GHz × 8 
Graphics: Intel® Ivybridge Mobile / GeForse 740m

Once again, thanks for all your helping.

Posted: **Mon Jul 06, 2015 12:07 pm**

Ok, thanks for the info.
I think I can easily add the detection of your device and provide a 64bit dmxusb.so plugin, but then how should we send data to it ?
We can try to consider it as a Enttec Open, but I'm not sure if it will work.

Posted: **Mon Jul 06, 2015 12:44 pm**

Ok, so you say that isn't enough to adding the line of this device on z65-dmxusb.rules file as a generic FTDI device?

If you agree i could try to do it tonigh a give you some feedback before modify the code behind the plugin dmxusb.so.

Thanks in advance!

Posted: **Mon Jul 06, 2015 12:44 pm**

nfs5cgd wrote:Ok, so you say that isn't enough to adding the line of this device on z65-dmxusb.rules file as a generic FTDI device?

Definitely not. The detection is performed in the C++ code. Udev rules are only to allow user access to the device.

Give me some time to make the proper change and I'll share the .so here.

Posted: **Mon Jul 06, 2015 1:18 pm**

Here, try this one. Must be placed in /usr/lib/qt4/plugins/qlcplus/

Add also this to the udev rule:
SUBSYSTEM=="usb*", ACTION=="add|change", ATTRS{idVendor}=="0403", ATTRS{idProduct}=="e088", MODE="0666"

[EDIT] By the way I think this is the homepage of the product: http://lienher.org/jean-marc/usb2dmx/index_en.html

Q Light Controller+

Issue with USB DMX512 OKSID

Issue with USB DMX512 OKSID

Re: Issue with USB DMX512 OKSID

Re: Issue with USB DMX512 OKSID

Re: Issue with USB DMX512 OKSID

Re: Issue with USB DMX512 OKSID

Re: Issue with USB DMX512 OKSID

Re: Issue with USB DMX512 OKSID