Q Light Controller+

Hello,

I am working on an application where I need to take ASCII data coming into the raspberry pi on a USB to RS232 adapter and trigger functions in QLC+.
I have already accomplished something similar using i2c Input modules and a shell script which translates input states into OSC messages sent to local host to trigger functions.

The issue I am having when I attempt this with the serial adapter is that QLC is recognizing the FTDI based serial adapter as a valid interface and is preventing the functions in my script from using the port.

Is it possible to configure QLC+ to ignore a certain device so that I can use the port from my script? Or maybe I can allocate the port during boot somehow prior to QLC+ starting??

I should also note that I am controlling DMX light fixtures with a USB to DMX adapter which shows up in QLC+ as the same type of USB to DMX adapter only with a different serial number.

Thanks for any help,

Simply (re)move the dmxusb plugin file
It's in /usr/lib/arm-linux-gnueabihf/qt5/plugins/qlcplus/libdmxusb.so

I should also note that I am controlling DMX light fixtures with a USB to DMX adapter which shows up in QLC+ as the same type of USB to DMX adapter only with a different serial number.

If I remove the dmxusb plugin entirely, will I still be able to use the USB to DMX adapter to control the lights?

No

Is it possible to configure QLC+ to ignore a certain device so that I can use the port from my script? Or maybe I can allocate the port during boot somehow prior to QLC+ starting??

I'm not sure what method you are using to start QLC+ on boot and cannot find it in the documentation supplied with the image I purchased. Can you tell me how this is happening so I can determine a way to open the serial port prior to QLC+ starting?

Also, does the DMXUSB plugin perform any sort of port availability verification or will it just try to open any ports found in /dev?