Q Light Controller+

Hi all,

I am new to the forums, so please excuse me if this has been discussed in detail already. I am working on a lighting system for a demo room, utilising the excellent QLC+ on the raspberry pi. The basic functionality works seamlessly, however, we currently have a control system designed by RTI built into the room, and I am working on integrating this with the PI. First thoughts were using an Artnet driver, but this isn't currently available for the RTI system, so I went looking into PI control via the RTI panel we have. SSH wasn't viable as we don't want the login handshake to affect the calling up of lighting ques. Consequently, I have succeeded in sending shell commands to the pi via TCP/IP, however, I cannot (yet) work out how to send a shell command that will fire off my virtual console buttons.

Can anyone help on this one?

Best wishes.

Budblinkin

Hello,

- If ArtNet is not available on the RTI system, maybe OSC or E1.31 are ?

- From the raspi command line, I guess you can send OSC commands to QLC+ with netcat.

Hi there, thanks for getting back to me,

Unfortunately, OSC and E1.31 are also unavailable, however, it is Netcat that I am currently using. I also just noticed in another area in the forum about the OSC commands. I will investigate this now.

Sorry for asking an already discussed question! Thanks again,

Update :

I have had a play with the OSC commands, they do work, but it becomes quite clunky when running a moving show, it seems backwards to send all that DMX data, to then relay it out to the lighting rig, when the Virtual console button does all that (pre configured) from the web browser. I guess I would need to mimic the press of the html button, via a TCP/IP string. hmm...

I am still learning on all of this, so please someone say if I am doing something silly.

You may try also: http://qlcplus.org/Test_Web_API.html if webinterface is enabled.

Thank you, I hadn't seen that, I will investigate and let you know how it goes!

Best wishes,

Hi All,

So I have managed to trigger the interface with a websocket (like what is used on the test page), and it works to a point,

I can go to a websocket client, connect to the PI interface, and send (for example) 23|255. This causes button 23 to be 'clicked' and it's great.

However, when I try and connect from my control systems Websocket client, it doesn't appear to work.

I've sniffed what is being transmitted from the control system and it does output the data (i think) correctly.

I can only think that the carriage return is not being transmitted correctly,

Anyone have any ideas on this?

Best wishes