When I started with my Raspberry Pi as DMX controller with the QLC+ software, it didn’t worked correct.

Together with the help of BitWizard company I find a way to get a functional DMX controller.

Maybe this document can help somebody else too.

Hardware :

Raspberry Pi

DMX interface from BitWizard

2x LED PAR56 spot

SD card with QLC+ software version : qlcplus_raspbian_wheezy_20151213

Monitor, keyboard, mouse, internet connection

The QLC+ software automatically start on boot.

First step is to connect the UART/DMX interface board to an universe in the QLC+ software.

Go to the tab Inputs/Outputs and select :  UART 1:ttyAMA0 Output.


Via the Simple Desk tab, you should be able to control your DMX fixture. At least when you now a correct channel. In my case the first channel is Red on the first PAR56 spot.

Probably you will notice that the response time is not good.

To solve this you need a working internet connection on the Rpi.

You can skip this step and go direct to the UPGRADE step below

if you already have a internet connection on the Rpi.


I changed the Rpi from fixed ip address  to DHCP.

Quit the QLC+ software by : Ctrl + Alt + Backspace

Log in as root with the default password raspberry.

Stop and start the network service using these commands :

# /etc/init.d/networking stop

# /etc/init.d/networking start

# ifconfig eth0 up

# mv /etc/network/interfaces  /etc/network/interfaces_fixed_ip

Create a file  /etc/network/interfaces  with these lines :

auto lo

iface lo inet loopback

allow-hotplug eth0

iface eth0 inet dhcp

And run the command :

ifconfig eth0 up

Now you should have a local IP address and connection to the internet on the Rpi.


When you didn’t change the directory, you see two files when you show the listing.



Upgrade the Rpi with the command :


That’s all.

The response time problem is solved.

note : I still have a problem when I give the reboot command.

But when I switch off and on again, everything is working correct again.

This is something which I will try to fix this in the future.

Some of the links I used to make this documentation :